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.