RMIRegistry and OutOfMemoryError
843793May 29 2004 — edited Jun 1 2004I am running a server process that registers 5 RMI Objects with the RMIRegistry that is running as a separate process on default port 1099. Initially, the client process is able to lookup (using Registry.lookup()) these RMI Objects from RMIRegistry and everything works fine, but after a period of 3 days of continuous run, the client process gets an exception java.rmi.NoSuchObjectException when it looks up for these RMI Objects. If I use the Registry.list() API, I can see the name of those 5 RMI Objects listed.
In these 3 days, the Server goes thru a lot of stress and I suspect that it may be leaking memory. I cannot see it since the process is running in background and I do not handle this exception. There is no core dump and the server process is still running.
My question is that what if the behaviour of rmiregistry process when the server process leaks memory and starts throwing OutOfMemoryError.
I am using JDK1.4.0 on HP-UX 11i.
Any help would be appreciated.