My Oracle Support Banner

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 FEBRUARY 11, 2024

Applies to:

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

Symptoms

Analyzing the OMS patch is failing with the below error:

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: <MIDDLEWARE_HOME>/OMSPatcher/omspatcher apply -analyze -invPtrLoc <MIDDLEWARE_HOME>/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:

OMS_HOME/cfgtoollogs/opatch/opatch<dateTimestamp>.log

[Feb 22, 2017 11:12:21 AM] --------------------- Get weblogic Admin Server information ---------------------
Please enter OMS weblogic admin server URL(t3s://<ADMINSERVER_HOSTNAME>:<ADMINSERVER_PORT>):> Please enter OMS weblogic admin server username(weblogic):> Please enter OMS weblogic admin server password:> <Feb 22, 2017 11:12:34 AM AEDT> <Info> <Security> <BEA-090905> <Disabling the CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true.>
<Feb 22, 2017 11:12:34 AM AEDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<Feb 22, 2017 11:12:34 AM AEDT> <Info> <Security> <BEA-090908> <Using the default WebLogic SSL Hostname Verifier implementation.>
<Feb 22, 2017 11:12:35 AM AEDT> <Warning> <Security> <BEA-090504> <Certificate chain received from <ADMINSERVER_HOSTNAME> - <IP_ADDRESS> failed hostname verification check. Certificate contained <ADMINSERVER_HOSTNAME>.abc.com but check expected <ADMINSERVER_HOSTNAME>>
[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://<ADMINSERVER_HOSTNAME>:<ADMINSERVER_PORT>: Destination <IP_ADDRESS>, <ADMINSERVER_PORT> unreachable; nested exception is:
javax.net.ssl.SSLKeyException: Hostname verification failed: HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier, hostname=<ADMINSERVER_HOSTNAME>.; 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: <MIDDLEWARE_HOME>/OMSPatcher/omspatcher apply -analyze -invPtrLoc <MIDDLEWARE_HOME>/oraInst.loc OMSPatcher.OMS_DISABLE_HOST_CHECK=true)

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

 

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.