Operations Basics / Version 2506.0
Table Of ContentsApplications do not respond on request
Applications do not respond on request.
The CPU load of the applications is high, the thread dump shows threads that use
nio classes.
Possible cause:
Problems with the CORBA ORB.
Possible Solution:
Add the following ORB property as a system property for the affected applications:
-Dcom.sun.corba.ee.transport.ORBUseNIOSelectToWait=false
CORBA Timeout for large copy operation e.g. when deriving a site
A large recursive copy operation like deriving a site fails on the client side with a warning like this after 12 hours:
org.omg.CORBA.COMM_FAILURE: WARNING: 00410019: Communications timeout waiting for response.
and the stacktrace (on DEBUG level) contains:
com.coremedia.cotopaxi.corba.CorbaContentConnector.copyRecursivelyToInternal
Cause:
The CORBA client ran into a timeout when waiting for the copy operation to finish.
Solution:
Increase the specific timeout for the copy operation (default: 43,200,000 (12 hours)) by setting the
environment variable COM_COREMEDIA_CORBA_COPY_RECURSIVELY_TIMEOUT_MILLIS.
CORBA Timeout for other operations
A CORBA operation fails on the client side with a warning like this:
org.omg.CORBA.COMM_FAILURE: WARNING: 00410019: Communications timeout waiting for response.
Cause:
The CORBA client ran into a timeout when waiting for the operation to finish.
Solution:
Increase the global CORBA timeout (default: 1,800,000 (30 min)) by setting the system property
com.sun.corba.ee.transport.ORBWaitForResponseTimeout.


