Known Issues with Move to Log4j2

(Doc ID 2336917.1)

Last updated on JANUARY 03, 2018

Applies to:

Oracle Utilities Network Management System - Version 1.12.0.3 to 2.3.0.1.0 [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version 1.12.0.3 to 2.3.0.1.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.

Symptoms



Known issues on move to log4j2. 

Log4j2 was introduced in 1.12.0.3.30/2.3.0.0.9/2.3.0.1.1.  The following problem was found with updating to log4j2.

When using client installers, logging does not appear to be functioning. The NMS client log file is created but is never written to.

Trying to enable any debug from the debug dialog in a running NMS installed version gives an error:

 log4j:ERROR Parsing error on line 2 and column 30
 log4j:ERROR Document root element "Configuration", must match DOCTYPE root "null".
 log4j:ERROR Parsing error on line 2 and column 30
 log4j:ERROR Document is invalid: no grammar found.
 log4j:ERROR DOM element is - not a element.
 log4j:WARN No appenders could be found for logger (com.bea.console.preferences.spi.FilePreferencesProvider).
 log4j:WARN Please initialize the log4j system properly




Changes

 Migrated to log4j2 with recent patch update.

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