EM 13c:OMSPatcher Failed to Establish JMX Connection to Weblogic Server with Error "javax.net.ssl.SSLKeyException: Hostname verification failed" (Doc ID 2236199.1)

Last updated on MARCH 12, 2017

Applies to:

Enterprise Manager Base Platform - Version 13.1.0.0.0 and later
Information in this document applies to any platform.

Symptoms

EM 13c(13.1)

Customer is trying to apply a PSU patch.

Patch analyze fails with following message:
OMSPatcher failed to establish JMX connection to weblogic server. This could be because of one (or) more of the following reasons:
1. Weblogic admin server URL that manages OMS application may not be right.
2. Weblogic admin server credentials (username, password) may not be right.
3. Virtual host configuration. If OMS, weblogic server are on virtual host configuration, Please make sure to add OMSPatcher.OMS_DISABLE_HOST_CHECK=true to command line and run again. (example: /u01/app/oraoem/middleware/OMSPatcher/omspatcher apply -analyze -invPtrLoc /u01/app/oraoem/middleware/oraInst.loc OMSPatcher.OMS_DISABLE_HOST_CHECK=true)

Please check above conditions and if error(s) still persist, Please contact Oracle support.

 

Following errors are seen in the opatch<dateTimestamp>.log:

[Feb 22, 2017 11:12:35 AM] --------------------- Get weblogic Admin Server information ---------------------
[Feb 22, 2017 11:12:35 AM] Stack Description: java.io.IOException: t3s://<ABCHOST>:7102: Destination 10.2.33.444, 7102 unreachable; nested exception is:
javax.net.ssl.SSLKeyException: Hostname verification failed: HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier, hostname=ABCHOST.; No available router to destination
[Feb 22, 2017 11:12:35 AM] StackTrace: weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:237)
[Feb 22, 2017 11:12:35 AM] StackTrace: weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:120)
[Feb 22, 2017 11:12:35 AM] StackTrace: javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:369)
[Feb 22, 2017 11:12:35 AM] StackTrace: javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:267)
[Feb 22, 2017 11:12:35 AM] StackTrace: oracle.opatchauto.oms.nodeframework.ProductDriverWrapper.initGCProductDriver(ProductDriverWrapper.java:334)
[Feb 22, 2017 11:12:35 AM] StackTrace: oracle.opatchauto.oms.nodeframework.ProductDriverWrapper.init(ProductDriverWrapper.java:214)
[Feb 22, 2017 11:12:35 AM] StackTrace: oracle.opatchauto.oms.OMSApplySession.process(OMSApplySession.java:318)
[Feb 22, 2017 11:12:35 AM] StackTrace: oracle.opatchauto.oms.OMSPatchingSession.main(OMSPatchingSession.java:672)
[Feb 22, 2017 11:12:35 AM] StackTrace: oracle.opatchauto.oms.OPatchAuto.main(OPatchAuto.java:795)
[Feb 22, 2017 11:12:35 AM] OMSPatcher failed to establish JMX connection to weblogic server. This could be because of one (or) more of the following reasons:
1. Weblogic admin server URL that manages OMS application may not be right.
2. Weblogic admin server credentials (username, password) may not be right.
3. Virtual host configuration. If OMS, weblogic server are on virtual host configuration, Please make sure to add OMSPatcher.OMS_DISABLE_HOST_CHECK=true to command line and run again. (example: /u01/app/oraoem/middleware/OMSPatcher/omspatcher apply -analyze -invPtrLoc /u01/app/oraoem/middleware/oraInst.loc OMSPatcher.OMS_DISABLE_HOST_CHECK=true)

Please check above conditions and if error(s) still persist, Please contact Oracle support.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms