My Oracle Support Banner

EM13c : Secure WLS with Custom Certs causes OEM Console Inaccessible (Doc ID 2449722.1)

Last updated on AUGUST 01, 2020

Applies to:

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

Symptoms

In Enterprise Manager (EM) Cloud Control, Customer trying to secure the EM WLS with Custom Certs makes the OEM Console inaccessible.

1. Secure WLS completed without issues.
2. OMS starts without issues.
3. Admin Server Console is accessible.
4. EM Console access fails with "Unable to connect"

+ Enabling the TRACE:32 debug on OHS using the steps documented in <Document 1662112.1>, gives the following error stack in <EM_INSTANCE_HOME>/config/fmwconfig/components/OHS/ohs1.log file:

[2018-07-09T16:07:26.7827-05:00] [OHS] [ERROR:32] [OHS-9999] [mod_weblogic.c] [host_id: <Hostname>] [host_addr: <IPAddress>] [tid: <TID>]
[user: <USER>] [ecid: <ECID>] [rid: <RID>] [VirtualHost: main] orassl.cpp:73: weblogic: SSL Handshake failed

[2018-07-09T16:07:26.7827-05:00] [OHS] [ERROR:32] [OHS-9999] [mod_weblogic.c] [client_id: <IPAddress>] [host_id: <Hostname>] [host_addr: <IPAddress>] [tid: <TID>] [user: <USER>] [ecid: <ECID>] [rid: <RID>] [VirtualHost: <Alias_Hostname>:0] URL.cpp:1817:
<ECID> <USER>: *******Exception type [NO_RESOURCES] (Could not open secure connection) raised at line 1817 of URL.cpp

+ Setting the following environment variables in <EM_INSTANCE_HOME>/config/fmwconfig/components/OHS/ohs1/ohs.plugins.nodemanager.properties to collect NZ ssl logs.

 

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
References


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