Weblogic Server (WLS) Log Levels For DIP Do Not Persist After Server Restart, A Previous Log Level Reverts Back Automatically
Last updated on OCTOBER 13, 2016
Applies to:Oracle Internet Directory - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Oracle Internet Directory (OID) 11g, i.e., 188.8.131.52, with the corresponding/compatbiel Weblogic Server (WLS), i.e., 10.3.5.0.
(Reference: <Document 1151602.1> How to Check Oracle Fusion Middleware 11g and WebLogic Component Versions?)
DIP application logging is always set to a previously set larger value, such as TRACE:32 FINE, after server start. Even after it is changed, it reverts back to the higher value after the server is restarted.
While OID is running, as soon as the log levels are changed, i.e. in Enterprise Manager (EM) Fusion Middleware (FMW) Control console, the tracing does stop in the logs, so it is taking effect correctly real time. However it reverts to trace level after a server restart.
Already tried the following, to no help:
- Selecting and/or not selecting the Persist checkbox at the bottom of the EM log configuration page, and ensuring the changes are saved by clicking Apply button.
- Stopping and restarting DIP Server.
- Switching from/to all the different logging levels, such as Notification, etc.
- Ensuring the desired log levels are saved, stopping DIP Server as well as WLS Managed Server then WLS Admin Server, backing up and removing existing logs, then restarting these components in the documented order.
- Although not supported/recommended, also tried manually backing up then adding the following DIP related section to $FMW_HOME/user_projects/domains/IDMDomain/config/fmwconfig/servers/wls_ods1/logging.xml (after taking a backup):
<logger name='oracle.dip.config' level='NOTIFICATION:1'/>
<logger name='oracle.dip.mbean.prov' level='NOTIFICATION:1'/>
<logger name='oracle.dip.mbean.sync' level='NOTIFICATION:1'/>
<logger name='oracle.dip.util' level='NOTIFICATION:1'/>
<logger name='oracle.ldap' level='NOTIFICATION:1'/>
But still, after any of the above, after restarting wls_ods1 the log level changes back to the higher level.
NOTE: As mentioned above, manually editing the logging.xml is not supported/recommended, but if documentation is needed, there is a small subsection that can be of interest in the following Developer's guide:
Oracle® Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework 11g Release 1 (184.108.40.206.0) Part Number B31974-10
Chapter 31 Testing and Debugging ADF Components
Section 31.5.5 What You May Need to Know About the Logging.xml File (Scroll down to the 31.5.5 section.)
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