OC4J Instance Restarted by OPMN Cannot be Accessed Through AS Console

(Doc ID 1199685.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 25-FEB-2013***

Symptoms


When a OC4J instance is failed and restarted by OPMN the AS console cannot be used to manage the instance until the AS Console has been restarted.

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