My Oracle Support Banner

ODSEE 11g: DSCC Uses LDAPS to Connect With Registered Instance and Shows Instance Stopped After Upgrading Tomcat's Java to 1.7.1_191 (Doc ID 2479971.1)

Last updated on OCTOBER 31, 2019

Applies to:

Oracle Directory Server Enterprise Edition - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

DSCC console (dscc7.war) is deployed on Tomcat 6 which uses JDK 1.7.0_40 installed in Windows machine.

After upgrading JDK of Windows machine from 1.7.0_40 to 1.7.0_191, not able to manage registered ODSEE instance through DSCC console.

DSCC uses LDAPS port to connect with registered instance.


ERROR:  DSCC console shows instance is stopped

 Note: Instance has been verified to be up and running from the backend.



Changes

 Upgraded JDK from 1.7.0_40 to 1.7.0_191

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
References


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