After Deploying a Plugin or Library, Plus Restarting OVD 11g Server, ODSM Connection Hangs or Fails with: Error ovdhost:8899 has failed SSL verification. Log May Show: SSL connection failed / java.net.ConnectException: Connection refused: connect (Doc ID 1585457.1)

Last updated on SEPTEMBER 01, 2017

Applies to:

Oracle Virtual Directory - Version 11.1.1.0 and later
Information in this document applies to any platform.

Symptoms

Oracle Virtual Directory (OVD) Server, i.e., 11.1.1.6.0.

Created and deployed a custom simple plugin, written as per steps mentioned in this Oracle whitepaper.

After deploying the custom plugin to OVD through Oracle Directory Services Manager (ODSM) console and restarting OVD Server, the next time ODSM attempts to connect to OVD, it fails with:

Error
myovdhost.mycompany.com:8899 has failed SSL verification. This may be due to a host address or port problem or trust could not be verified or was declined.


If OVD is not restarted after the plugin deployment in ODSM > Advance -> Libraries, then ODSM continues to work.  The problem occurs only after deploying the custom plugin and restarting OVD Server afterwards.

The following exception is shown in the WLS diagnostic log file:

[2013-04-25T13:08:27.022-04:00] [wls_ods1] [ERROR] [] [oracle.ldap.odsm.ui.common.Login] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 017ebde441907d58:-6de7f2fa:13e422904bb:-8000-000000000000001c,0] [APP: odsm#11.1.1.2.0]  [ODSM-00007] SSL connection failed.
[2013-04-25T13:08:27.033-04:00] [wls_ods1] [ERROR] [] [oracle.ldap.odsm.ui.common.Login] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: 017ebde441907d58:-6de7f2fa:13e422904bb:-8000-000000000000001c,0] [APP: odsm#11.1.1.2.0] Connection refused: connect[[
java.net.ConnectException: Connection refused: connect


Another related ODSM behavior can be more easily reproduced by the following steps:

1. Download and extract the log4j-1.2.16.jar from one of the zip files available at http://archive.apache.org/dist/logging/log4j/1.2.162. Connect to OVD through ODSM
3. Go to Advanced tab > Libraries section and upload the extracted log4j-1.2.16.jar file
4. Refresh the Libraries and make sure that log4j-1.2.16.jar is uploaded as Library
5. Restart OVD server
6. Attempt to connect to OVD via ODSM, and it hangs indefinitely with no error messages

The following may also be seen in the log:

Could not find partial trigger latIT from RichTable[org.apache.myfaces.trinidad.component.UIXTable$RowKeyFacesBeanWrapper@b855b4, id=t4] with the supported partialTriggers syntax. The partial trigger was found with the deprecated syntax. Please use the supported syntax.


Tried the following Notes' solutions to no help:
After Upgrading to 11.1.1.2, ODSM Connecting To OVD 11g Admin SSL 8899 Port Fails With: Error Server :8899 Has Failed SSL Verification <Document 1369765.1>
ODSM Connecting To OVD 11g Admin Port In SSL Mode Fails With Error Server :8899 Has Failed SSL Verification <Document 1269135.1>


Workaround:
- Delete the custom plugin and log4j.jar (all jar files deleted from $ORACLE_INSTANCE/OVD/plugins/lib).
- Restart OVD server.
- Close the browser and open a new ODSM console, and ODSM will connect to OVD.
- Then re-upload the custom plugin and log4j.jar in the Advanced tab.
- Do not restart OVD server from then on out, or the problem will reoccur.

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