[
https://jira.jboss.org/jira/browse/JBAS-5197?page=com.atlassian.jira.plug...
]
Brian Stansberry commented on JBAS-5197:
----------------------------------------
If there were a JIRA Fix Version 5.X where X != 0.1 or 1.0 I'd put it there. But
there's not and I'm not committing to do it in the next release which should come
out in a few months. So it goes to the next choice which is 6. There's a discussion of
roadmap on jboss-dev list that started about 10 days ago; will likely pick up next week; I
encourage you to give your input. Coming out of that either AS 6 will be fairly soon on
the roadmap or there should be more 5.x releases in JIRA to which I can assign this.
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.Alpha1
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