My Oracle Support Banner

Oracle Http Server Status Shows as "UNKNOWN" in FMW Control After AdminServer's Default Keystore is Changed. (Doc ID 2236872.1)

Last updated on OCTOBER 15, 2018

Applies to:

Enterprise Manager for Fusion Middleware - Version 12.1.2.0.0 to 12.2.1.2.0 [Release 12c]
Oracle Internet Directory - Version 12.2.1.3.180621 to 12.2.1.3.180621 [Release 12c]
Information in this document applies to any platform.

Symptoms

The OHS state is showing as "UNKNOWN" after changing the Keystore from Demo Identity and Demo Trust to Custom Identity and Java Standard Trust

 The following errors will be logged in AdminServer-diagnostics.log

[2017-02-24T21:15:36.863+05:30] [AdminServer] [ERROR] [] [oracle.ohs.mbeans] [tid: [ACTIVE].ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 3243e719-1408-479b-9360-458cdb116b3e-0000008d,0] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: 0000Ldkkhso0JvH_Mt_Aie1Og5AD000002] Node manager is not accessible[[
java.lang.Exception: Node manager is not accessible
at oracle.ohs.OHSTypeInfo.getInstanceProperties(Unknown Source)
at oracle.ohs.OHSTypeInfo.getInstanceProperties(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

[2017-02-24T21:15:37.022+05:30] [AdminServer] [ERROR] [] [oracle.ohs.mbeans] [tid: [ACTIVE].ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 3243e719-1408-479b-9360-458cdb116b3e-0000008d,0] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: 0000Ldkkhso0JvH_Mt_Aie1Og5AD000002] General SSLEngine problem[[
javax.net.ssl.SSLHandshakeException: General SSLEngine problem
at sun.security.ssl.Handshaker.checkThrown(Handshaker.java:1431)
at sun.security.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:535)
at sun.security.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1214)

                                  

 

Changes

 Enabled SSL for AdminServer and Changed the Keystore from Demo Identity and Demo Trust to Custom Identity and Java Standard Trust

   1) Loged in to AdminServer Console

   2) Selected Servers --> AdminServer

             In the General Tab   --> Selected "SSL Listen Port Enabled"

             In the Keystores tab --> Selected Keystore as Custom Identity and Java Standard Trust

                                        --> Provided Custom Identity Keystore location ==> eg: C:\Users\vpps\Downloads\apo-signature.jks

                                        --> Provided Custom Identity Keystore Type ==> eg: jks

                                        --> Provided Custom Identity Keystore Passphrase

                                        --> Provided Java Standard Trust Keystore ==> eg:- C:\PROGRA~1\Java\JDK18~1.0_1\jre\lib\security\cacerts

              In the SSL tab       --> Provided Private Key Alias ==> eg: slnxamue9

                                        --> Provided Private Key Passphrase

   3) Saved and Activated the changes

   4) Able to access AdminServer on SSL

Reference: Getting Started with WebLogic Server: How to Configure SSL on Oracle WebLogic Server with Custom Identity and Java Standard Trust (Doc ID 1109753.1) 

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
Changes
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.