]
Brian Stansberry closed JBAS-4740.
----------------------------------
Resolution: Done
HARMIClient to give preference to wrapping NoSuchObjectException
----------------------------------------------------------------
Key: JBAS-4740
URL:
http://jira.jboss.com/jira/browse/JBAS-4740
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Minor
Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA
HARMIClient catches a number of java.rmi exception types that indicate a request did not
reach the server. It then attempts to failover, and keeps catching exceptions until all
targets are exhausted. If all targets are exhausted, the last exception caught is wrapped
in a RemoteException and thrown.
This issue is to specially cache any java.rmi.NoSuchObjectException. If all targets are
exhausted and an NSOE was caught, we wrap that instead of the last exception caught.
Intent here is the NSOE provides information that a target server is listening on the
given port but that the client-side naming stub is out of sync with the server-side RMI
runtime. This is potentially useful to the caller; e.g. see the parent issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: