[jboss-dev-forums] [Design of Clustering on JBoss] - Re: Handling soft versus hard pooledInvoker exceptions in JR

[bstansberry@jboss.com]

Agreed about safety in the 4.x releases.  These are client-side classes and 4.x is in micro-release mode with possibly older releases trying to communicate with any 4.2.4 this would go into.  Adding new classes would break such clients.

It's probably about too late to add new classes to 5.x as well, as the CR2 is about to go out.

I think what you propose looks OK; it basically mimics the behavior of the finally "catch (Exception e)" block in JRMPInvokerProxyHA.invoke(). AFAICT, only side effect it would have would be to prevent failover if java.rmi.ConnectException(cause EOFException) were returned from the server side.  And if that happened, preventing failover is probably the right thing to do anyway.

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

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