Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Performance Explorer fails to connect to WebLogic due to a timeout

Performance Explorer fails to connect to WebLogic due to a timeout

Due to a known issue in the Java JDK, Performance Explorer can fail to connect to WebLogic servers because of a timeout.

When a connection fails to be established, Performance Explorer should report the exception. If the stacktrace exception contains both the values  "transportReadTimeoutExceeded" & "CORBA COMM_FAILURE 1398079696", then this is likely caused by the JDK bug 5086952.

To workaround the problem, it should be possible to add the additional JVM parameter -Dcom.sun.CORBA.transport.ORBTCPReadTimeouts=100:15000:300:5 to Performance Explorers JMX connection command.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-07-23 14:09
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.