[
https://jira.jboss.org/jira/browse/JBAS-5197?page=com.atlassian.jira.plug...
]
Armin Haaf commented on JBAS-5197:
----------------------------------
WOW, this is really a basic functionality for a cluster environment.
We are migrating to jboss 5.1 cluster and cannot believe this problem. This will be hard
to tell our customers, they have to wait another x years....
The issue is known 1 year now ...
Add "RetryInterceptor" functionality to all clustered
proxies
-------------------------------------------------------------
Key: JBAS-5197
URL:
https://jira.jboss.org/jira/browse/JBAS-5197
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M3
Container issue for ensuring "RetryInterceptor" functionality is added to all
clustered proxies.
"RetryInterceptor" functionality consists of adding an interceptor that is able
to access the cluster (currently via JNDI) and get an updated set of cluster targets when
all current targets have failed. Needed when a complete cluster restart has occurred
since the current list of targets was deserialized on the client.
We currently have this for EJB2 proxies; need it for EJB3, HA-JNDI and generic AOP-based
and ProxyFactoryHA-based proxies.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira