The legacy detached invoker framework 
org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxyHA is throwing a 
java.rmi.RemoteException when all cluster targets have been exhausted. I 
updated the proxy factories to expose the raw invoker so that one can add a 
retry interceptor to the client proxy stack to transparently recover from a 
transient loss of all cluster services as in the case of a complete cluster 
restart.

The problem with the use of the java.rmi.RemoteException is that this is an 
exception that can be thrown as part of the normal application behavior and so 
is not a reliable indication of services exhaustion. We should be throwing a 
custom subclass of RemoteException like 
org.jboss.invocation.ServiceUnavailableException to clearly distinguish this 
failure scenario.

I'm going to make this change in head so I can check in a prototype 
RetryInterceptor that requires this.



View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862618#3862618

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862618


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to