Logfile "log.xml" Stops Collecting Information Because The Configuration File "j2ee-logging.xml" Is Inconsistent After Setting The Level Of "oracle" Logger To NULL And Reverting (Doc ID 1265685.1)

Last updated on DECEMBER 05, 2016

Applies to:

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

Symptoms

In Oracle Application Server 10gR3 or OC4J based environment, the main log file file log.xml stops collecting information and is not updated anymore.

Changes

The problem occurs when in ASControl, the log level for the logger "oracle" has been set to NULL voluntarily or accidentaly.

After setting it back the log level to its original value, or to any other log level as INFO, CONFIG, WARN, etc .. the logging functionality does not recover and the log file still does not receive any logged message.


The problem can be reproduced for testing very easily with following actions:

1) Create a testing oc4j instance


is inserted, but there is no "<handler" tag any more. 

As there is no handler associated to the logger, the log file will never be populated with logging information.

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