Unable to Stop the Managed Server and Admin Server Using stopManagedWebLogic.sh and stopWebLogic.sh After Enabling SSL for the Admin Server

(Doc ID 2315671.1)

Last updated on OCTOBER 18, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.

Symptoms

The following error occurs when running stopWebLogic.sh to stop the Admin server or running stopManagedWebLogic.sh to stop the managed server:

Connecting to t3s://host.domain.com:8001 with userid weblogic ...
<Sep 15, 2017 3:43:33 PM BST> <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.>
<Sep 15, 2017 3:43:33 PM BST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG128 to HMACDRBG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true.>
<Sep 15, 2017 3:43:33 PM BST> <Info> <Security> <BEA-090908> <Using the default WebLogic SSL Hostname Verifier implementation.>
<Sep 15, 2017 3:43:35 PM BST> <Warning> <Security> <BEA-090504> <Certificate chain received from host.domain.com - 10.21.1.42 failed hostname verification check. Certificate contained otherHost.domain.com but check expected host.domain.com>
This Exception occurred at Fri Sep 15 15:43:35 BST 2017.
javax.naming.CommunicationException: Failed to initialize JNDI context, tried 1 time or times totally, the interval of each time is 0ms.
t3s://host.domain.com:8001: Destination 10.21.1.42, 8001 unreachable.; nested exception is:
javax.net.ssl.SSLKeyException: Hostname verification failed: HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier, hostname=host.domain.com.; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination. [Root exception is java.net.ConnectException: t3s://host.domain.com:8001: Destination 10.21.1.42, 8001 unreachable.; nested exception is:
javax.net.ssl.SSLKeyException: Hostname verification failed: HostnameVerifier=weblogic.security.utils.SSLWLSHostnameVerifier, hostname=host.domain.com.; No available router to destination.; nested exception is:
java.rmi.ConnectException: No available router to destination.]
Problem invoking WLST - Traceback (innermost last):
File "/usr/Oracle_Home/config/domains/pulse_domain/shutdown-AdminServer.py", line 3, in ?
File "<iostream>", line 19, in connect
File "<iostream>", line 553, in raiseWLSTException
WLSTException: Error occurred while performing connect : Cannot connect via SSL. To connect via SSL, use the following two System properties as shown, java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST : Failed to initialize JNDI context, tried 1 time or times totally, the interval of each time is 0ms.



Changes

 

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