JMS API Code with log4j Logging Enabled on Client Disregards JMS Logging Level (Doc ID 1025110.1)

Last updated on NOVEMBER 02, 2016

Applies to:

Sun Integrated Composite Application Network (ICAN) - Version: 5.0.5 and later   [Release: and later ]
Information in this document applies to any platform.
Checked for relevance on 13-May-2011.

Symptoms

When using log4j logging in the client side code of the JMS API Kit, DEBUG messages from the com.stc.jms classes are being written to the client log regardless of the fact that the following line has been set in the log4j.properties file:

logj4.logger.com.stc.jms=ERROR

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