RMI Clients Cannot talk to the RMI Server Object if left running for a long time.
posted 11 years ago
Hi, This is my situation. I have an java app that creates an remote object(lets call this app as Server).This RMI object will be called by some other applications. The server app will launch other JVMs(client apps) which in turn will talk to the server app(meaning talk to the remote object).
I leave the server and client application running for a long time.(overnight). The next day if close the already running the client apps, and start new clients apps(the server app will launch the new client apps), and if they try to talk to the remote object, they get the "connection refused" exception. There is no problem in starting the new client JVMs, only when they try to communicate with the remote object, the problem occurs.
This happens only at the customer place when they leave the application running for a long time. I cannot reproduce the problem in my development or my test pcs. Could someone give some lead into this problem. Is there any other RMI property I need to set. I tried setting the sun.rmi.transport.tcp.readTimeout(default is 2 hours, I set it to 5 minutes to recreate the issue, but no use).