[GLASSFISH-5815] RAR redeploy issue Created: 02/Sep/08  Updated: 22/Jan/11  Resolved: 22/Jan/11

Status: Resolved
Project: glassfish
Component/s: jca
Affects Version/s: 9.1peur1
Fix Version/s: V3

Type: Improvement Priority: Major
Reporter: dernasherbrezon Assignee: Jagadish
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 5,815

 Description   

Real scenario in production environment:

1. Deploy RAR connector
2. Configure adapter resources &etc
3. Deploy 40 endpoint clients - some MDBs. (Real production scenario )

after some time...

4. redeploy rar to fix bugs or upgrade - no matter.
5. redeploy 40 endpoint clients.

Does it possible to avoid step 5? or do it by app server automaticly? This will
increase availability of endpoint clients



 Comments   
Comment by Hong Zhang [ 21/Jan/11 ]

assign to jagadish for evaluation

Comment by Jagadish [ 22/Jan/11 ]

It is not possible for a transparent redeployment of rar and its associated (referring) applications as the classloader for the resource-adapter need to be re-created and the referring applications need to use the new resource-adapter classloader. Apart from this there may be references to connector resources that an application might have.

Marking as "Won't Fix" as there is no way to specify "Not an issue"

Generated at Tue Mar 28 18:34:00 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.