[
https://issues.apache.org/jira/browse/QPID-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu resolved QPID-2113.
------------------------------------
Resolution: Fixed
A log4j.xml file for the client module was added in rev 817457 on qpid trunk.
I didn't meddle with the existing log4j.properties file present in the common
module as it maybe used in the broker.
However a cursory glance at the etc directory revealed that the the broker too
has a log4j.xml file.
So perhaps the log4j.properties files in the common module is not really needed.
(The settings given i the log4j.xml under the client module could be overridden
by explicitly specifying a log4.xml file using -Dlog.configuration property)
> JMS client's default logging level should be WARN not DEBUG
> -----------------------------------------------------------
>
> Key: QPID-2113
> URL: https://issues.apache.org/jira/browse/QPID-2113
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.6
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: 0.6
>
>
> The way log4j works is as follows.
> It will try to look for log4j.xml within the classpath.
> Failing which it will try to look for log4j.properties within the classpath.
> In our qpid-common-xx.jar we have a log4j.properties and the log level is
> configured as follows.
> log4j.logger.org.apache.qpid=${amqj.logging.level}, console
> So unless the system property "amqj.logging.level" is set, it will default to
> DEBUG. (log4j unfortunately defaults to DEBUG instead of WARN).
> This causes an issue as out of the box performance for the JMS client is slow
> due to the excessive logging.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
