CDD Processing Units Tab Coherence Log Properties Reference

The properties in the Coherence Log Properties section are used to configure the Coherence log. This log is used only if Oracle Coherence is used as the cache provider.

Standard logging settings are configured in the Log Configuration tab. See CDD Collections Tab Log Configurations Settings Reference.

CDD Processing Units Tab Coherence Properties
Property Notes
Coherence Log Properties
tangosol.coherence.log
  Specifies the output device used by the logging system.

Optional.

Possible values are:

  • stdout
  • stderr
  • jdk (Requires JDK 1.4 or later)
  • log4j (Requires log4j libraries to be in the classpath)
  • A file path and file name

    If you specify jdk or log4j you must also perform appropriate configuration of the JDK or Apache log4J logging libraries.

    Default is stdout.

tangosol.coherence.log.level
  Specifies which logged messages are output to the log destination.

Optional.

Possible values are:

  • 0: Only output without a logging severity level specified will be logged
  • 1: All the above plus errors
  • 2: All the above plus warnings
  • 3: All the above plus informational messages
  • 4-9: All the above plus internal debugging messages (the higher the number, the more the messages)
  • -1: No messages

Default is 5.

tangosol.coherence.log.limit
  Specifies the maximum number of characters that the logger daemon processes from the message queue before discarding all remaining messages in the queue.

The message that causes the total number of characters to exceed the maximum is not truncated.

All discarded messages are summarized by the logging system with a single log entry detailing the number of discarded messages and their total size. When the queue empties, the logger is reset and subsequent messages are again logged.

The purpose of this setting is to avoid a situation where logging can itself prevent recovery from a failing condition, for example by contributing to timing issues.

Logging occurs on a dedicated low-priority thread to further reduce its impact on the critical portions of the system.

Optional.

Possible values are positive integers or zero (0). Zero implies no limit.

Default is 0

JMX Management properties

You must specify the following JMX-related properties to enable cluster statistics to appear in the monitored objects table in MM. (MM is not available in TIBCO BusinessEvents Express.)

tangosol.coherence.management
  Default is all
tangosol.coherence.management.remote
  Default is true