OC4J 10.1.3 Process Crashes with no Errors Reported in Container Log File (Doc ID 756513.1)

Last updated on OCTOBER 20, 2016

Applies to:

Oracle Containers for J2EE - Version 10.1.3.1.0 and later
Information in this document applies to any platform.

Symptoms

There are 2 OC4J 10.1.3.1.1 containers configured in a cluster.
On one of the cluster instances, a container crashes. The application (java application used to
authenticate users to web applications) under the container does not start up after the crash and
has trouble joining the cache (jgroups), for which it has to be restarted manually. When it is
restarted manually, it starts with no issues.

opmn.log file shows the container crashing :

08/12/04 23:07:29 [pm-process] Starting Process: default_group~SSO~default_group~1 (13:0)
08/12/04 23:07:41 [pm-process] Process Alive: default_group~SSO~default_group~1 (13:684)
08/12/04 23:07:41 [pm-requests] Request 1798 Completed. Command: /start?process-type=SSO
08/12/07 07:33:02 [pm-process] Process Crashed: default_group~SSO~default_group~1 (13:684) - Restarting
08/12/07 07:33:02 [pm-process] Starting Process: default_group~SSO~default_group~1 (14:0)
08/12/07 07:33:47 [pm-process] Process Alive: default_group~SSO~default_group~1 (14:7672)



Container log file default_group~SSO~default_group does not show  related errors to the crash.



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