How to Avoid 'Warning J2ee Ojr-01002' Message beeing Constantly Logged ? (Doc ID 942355.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Containers for J2EE - Version: 10.1.3.4.0 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.
***Checked for relevance on 04-Aug-2011***

Goal

After starting 10.1.3.4. OC4J,  the "WARNING J2EE OJR-01002 ' message is constantly logged:

2009-09-16 16:31:29.406 WARNING J2EE OJR-01002 The number of concurrent Timer has reached the
maximum limit: {0}
2009-09-16 16:31:29.722 WARNING J2EE OJR-01002 The number of concurrent Timer has reached the
maximum limit: {0}
2009-09-16 16:31:30.032 WARNING J2EE OJR-01002 The number of concurrent Timer has reached the
maximum limit: {0}
2009-09-16 16:31:30.342 WARNING J2EE OJR-01002 The number of concurrent Timer has reached the
maximum limit: {0}

As the result, OC4J log file  can grow to an unexpected big size.
The goal of this note is to avoid OC4J log file being filled by the OJR-01002 messages.

Solution

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