invocationHasReachedAServer calls within exception handling vary from UnifiedInvokerHAProxy to JRMPInvokerProxyHA ----------------------------------------------------------------------------------------------------------------- Key: JBAS-4963 URL: http://jira.jboss.com/jira/browse/JBAS-4963 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta3 Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Exception handling is different between JRMPInvokerProxyHA and UnifiedInvokerHAProxy when it comes to, at least, calls to invocationHasReachedAServer(): 1.- JRMPInvokerProxyHA Exception handling that does not lead to invocationHasReachedAServer() being called: * java.net.ConnectException * java.net.UnknownHostException * java.rmi.ConnectException * java.rmi.ConnectIOException * java.rmi.NoSuchObjectException * java.rmi.UnknownHostException * GenericClusteringException.NO Exception handling that leads to invocationHasReachedAServer() being called: * GenericClusteringException.YES * java.rmi.ServerException * java.lang.Exception 2.- UnifiedInvokerHAProxy Exception handling that does not lead to invocationHasReachedAServer() being called: * org.jboss.remoting.CannotConnectException * GenericClusteringException.NO * java.rmi.RemoteException * java.lang.Throwable Exception handling that leads to invocationHasReachedAServer() being called: * GenericClusteringException.YES This JIRA tracks discussions to clarify the correctness of UnifiedInvokerHAProxy and any potential coding required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira