Best Practices On How To Setup Coherence Logging in WebLogic Server 10.3 and 12.1.1 Environments
(Doc ID 1905099.1)
Last updated on AUGUST 18, 2022
Oracle Coherence - Version 3.5.3 and later Oracle WebLogic Server - Version 10.3.4 to 220.127.116.11 Information in this document applies to any platform.
This document describes best practices on how to setup Coherence logging in WebLogic Server 10.3.x and 12.1.1 environments.
Coherence logging of all Coherence cluster members at a sufficient log level is essential when analyzing a problem observed with a Coherence cluster.
By default Coherence prints log messages to "standard error".
Many upper layer Oracle Fusion Middleware products configure the managed WebLogic Server instances to start with the java system property:
which tells Coherence to use Java's logging infrastructure, java.util.logging (JDK 1.4 Logging API).
However, since those products don't provide specific configuration to properly setup java.util.logging, the ConsoleHandler will be used to print log messages to "System.err". As a result the Coherence log messages will appear on the operating system shell console or in the WebLogic Server managed Coherence Server out files only.
This document explains how to configure
WebLogic Servers to get Coherence log messages printed into the managed WebLogic Server log files with Coherence running in-process with the WebLogic Server instance,
Coherence Servers to get Coherence log messages printed into dedicated Coherence log files located in the log folder of the managed Coherence server for storage enabled Coherence instances used for an out-of-process topology.
Applications and upper layer Oracle Fusion Middleware products using Coherence with in-process, out-of-process or out-of-process with Coherence*Extend topology in WebLogic Server 10.3.x and 12.1.1 environments.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!