Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Obsolete
Priority: Major
Fix Version/s: No Release
Affects Version/s: None
Component/s: Clustering
Labels:
None

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

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.

is blocked by

JBAS-3765 AOP-based version of RetryInterceptor

Closed

EJBTHREE-1002 EJB3-based version of the RetryInterceptor

Open

is related to

JBAS-1476 Need to include a notion of cluster instance in the cluster view

Closed

Assignee:: Brian Stansberry

Reporter:: Brian Stansberry

Votes:: 4 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2008/02/01 10:54 AM

Updated:: 2020/09/14 5:33 AM

Resolved:: 2011/03/22 1:57 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates