[jboss-jira] [JBoss JIRA] Closed: (JBAS-4574) AS ejb ha restart would fail
[ http://jira.jboss.com/jira/browse/JBAS-4574?page=all ]
Adrian Brock closed JBAS-4574.
------------------------------
Resolution: Duplicate Issue
Ben. Please discuss problems in the forums before opening bug reports.
Or at least use search first before duplicating bug reports.
This is a duplicate of JBAS-1476
When you shutdown the server EJB2 you shutdown the whole cluster,
it ceased to exist.
When you started the server EJB1 you created a new cluster.
All clients are orhpaned by the shutdown of the whole cluster.
You either need to reget the client stubs (including the naming stub)
or introduce the RetryInterceptor in the client side to do this automagically:
http://wiki.jboss.org/wiki/Wiki.jsp?page=RetryInterceptor
JBAS-1476 would allow the client to automatically know when a cluster
was shutdown completely (assuming you are using a transport that
can recover from its entire view becoming invalid - i.e. not RMI).
AS ejb ha restart would fail
----------------------------
Key: JBAS-4574
URL: http://jira.jboss.com/jira/browse/JBAS-4574
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.0.5.GA
Reporter: Ben Wang
Assigned To: Ben Wang
This is an issue discovered during a pre-sales opportunity. Basically, it can be
reproduced like this:
1. Use a web tier (calling remote slsb ejb from jsp, e.g.) with 2 ejb tiers (for
clustering, say, ejb1, ejb2)
2. access it first to ejb1
3. shutdown ejb1, and access it again will failover to ejb2
4. shutdown ejb2 and bring up ejb1, should produce error traces (I don't have now).
Will attach it here later.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira