If you are using RMI calling, this exception java.rmi.NoSuchObjectException maybe come up after network failed.
Perhaps the root causation is an issue(or bug) of RMI: the binded implement object has been GCed by DGC protocol.
we can reference this URL for detail:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4114579
To reproduce this failure, we can break down the network connection on a Server for a while, then restore network and execute :
interface = Naming.lookup();
interface.methodName(); // NoSuchObjectException will throw out
To resolve this problem, you can add two classes RMIHelper, ServiceObjectKeeper to encapsulate RMI calling, and replace all old calling
Naming.rebind() with RMIHelper.rebind(), Naming.bind() with RMIHelper.bind().
Thus will hold a strong reference to the remote object in the local VM.
The following content is picked up from J2SDK, it point out Java have a hidden trouble on this topic.
Note that if a network partition exists between a client and a remote server object, it is possible that premature collection
of the remote object will occur (since the transport might believe that the client crashed). Because of the possibility of premature collection, remote references cannot guarantee referential integrity; in other words, it is always possible that a remote reference
may in fact not refer to an existing object. An attempt to use such a reference will generate a
RemoteException which must be handled by the application.
--- From J2SDK 1.4.1
Java Remote Method Invocation – 3.3 Garbage Collection of Remote Objects