Lately I was reminded of a case I solved last Summer: In this case one customer was facing the problem of an error message stating "RMIConnection Disconnected".
Problem
While monitoring the log files of OC4J we found that the called business method of the Session Bean took too long to respond to thecall from the client.
Solution
There are at least two ways to solve the problem:- make the business method to respond quicker (highly recommended)
- change the timeout value (with the property rmi.client.connection.timeout=<value_in_seconds>)
Comments (3)
In what file do you set the timeout value?
Posted by Kris Henneman | March 30, 2007 1:37 PM
Posted on March 30, 2007 13:37
Kris, this property is a command line property you can use -Drmi.client.connection.timeout=<value> in your startup script (for OC4J standalone) or in opmn.xml (for Oracle AS).
--olaf
Posted by Olaf Heimburger | April 2, 2007 12:51 AM
Posted on April 2, 2007 00:51
Thank you!
Posted by Kris Henneman | April 2, 2007 6:53 AM
Posted on April 2, 2007 06:53