OC4J Instance Fails To Start, No Error, Large JMS Persistence File (Doc ID 1348001.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Containers for J2EE - Version: 10.1.3.5.0 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Symptoms


An OC4J instance is failing to start but the log file does not show any errors. There is a large JMS persistence file in ORACLE_HOME/j2ee/<instance>/persistence/<group> directory.

For example if the instance is named test1 and the group is default_group, the location would be,

ORACLE_HOME/j2ee/test1/persistence/test1_default_group_1

The file name would be based on a topic or queue defined in the OC4J instance.

Changes

A large processing task may be being performed causing unusually large numbers of JMS messages to be stored.

The OC4J process may have been shutdown, or it failed due to out of memory or other conditions leaving the messages waiting to be processed.

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