I couldn't find any information on network related issues with RMI (specially in case of IPMP). I am really stuck at this point.RMI doesn't do anything startling with the network. Any other Java TCP client or server would experience the same failures. There's no reason to confine your search to RMI, or even to Java.
Note: Any such issue is never observed in non-IPMP setup.Then IPMP is what you should be investigating, not RMI.
All the java components are on different machines (solaris) and bind with the registry via UDP multicast.RMI components bind to the RMI Registry via TCP unicast.
1) How come the java components keep communicating? Because even they call remote methods on each other without any fail.I don't know what failures you were expecting so I can't answer that.
2) If there is any network interruption in between the RMI registry and the remote component, could it be possible that the skeletons in the list are no longer bound with the RMI registry?I don't understand the question. The only communication between the RMI Registry and remote objects occurs at bind time or else it consists of DGC calls. There are no skeletons in an RMI Registry, only stubs. The only way a stub can no longer be bound is if someone unbinds it or the Registry is restarted.
3) Its fine that such exceptions are being observed when there are network interruptions........ but even after its back to normal such exceptions are still being observed.Doesn't that mean there is still a network problem?
Just trying to figure out what happens with the registry in case of heavy network interruptions.Nothing special. It's just a TCP server really.