Nov 16th, 2006, 05:06 AM
Handling RMI ConnectException
The RmiProxyFactoryBean works great. But I'm puzzled as on how to handle java.net.ConnectException when a client tries to connect to a server that is not running.
I noticed that the RmiProxyFactoryBean inherits methods from org.springframework.remoting.rmi.RmiClientIntercep tor, such as <code>isConnectFailure</code>. But how can I take advantage of this?
The idea is to try to connect to another RMI server; i.e. create a minimal kind of failover.