You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2009/07/08 17:43:14 UTC
[jira] Created: (QPID-1975) Broker defaults to DEBUG for logging if
log4j.xml is not available
Broker defaults to DEBUG for logging if log4j.xml is not available
------------------------------------------------------------------
Key: QPID-1975
URL: https://issues.apache.org/jira/browse/QPID-1975
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: M4, M3, M2.1, M2, M1, 0.5
Reporter: Martin Ritchie
Fix For: 0.6
Summary:
Currently if the log4j configuration file is not present when the broker starts up then it will use a BasicConfigurator that defaults logging to DEBUG level.
Detail
A global DEBUG level will result generate so much logging that the broker will be overwhelmed if any volume of messages are sent.
The use of the BasicConfigurator can be seen in Main (L:490-495) If the requested log configuration file does not exist or cannot be read then a BasicConfigurator will be setup. This results in DEBUG level logging being enabled.
Change:
Setting the root logger level to WARN will set all logging to a more sensible WARN level
Logger.getRootLogger().setLevel(Level.WARN);
Testing:
This can be tested via an InVM test. Start the broker with a non existent log4j configuration file then:
Logger.getRootLogger().getLevel();
will currently return DEBUG. After the fix it will return WARN.
--
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-subscribe@qpid.apache.org
[jira] Closed: (QPID-1975) Broker defaults to DEBUG for logging if
log4j.xml is not available
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie closed QPID-1975.
--------------------------------
Resolution: Fixed
> Broker defaults to DEBUG for logging if log4j.xml is not available
> ------------------------------------------------------------------
>
> Key: QPID-1975
> URL: https://issues.apache.org/jira/browse/QPID-1975
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M1, M2, M2.1, M3, M4, 0.5
> Reporter: Martin Ritchie
> Fix For: 0.6
>
>
> Summary:
> Currently if the log4j configuration file is not present when the broker starts up then it will use a BasicConfigurator that defaults logging to DEBUG level.
> Detail
> A global DEBUG level will result generate so much logging that the broker will be overwhelmed if any volume of messages are sent.
> The use of the BasicConfigurator can be seen in Main (L:490-495) If the requested log configuration file does not exist or cannot be read then a BasicConfigurator will be setup. This results in DEBUG level logging being enabled.
> Change:
> Setting the root logger level to WARN will set all logging to a more sensible WARN level
> Logger.getRootLogger().setLevel(Level.WARN);
> Testing:
> This can be tested via an InVM test. Start the broker with a non existent log4j configuration file then:
> Logger.getRootLogger().getLevel();
> will currently return DEBUG. After the fix it will return WARN.
--
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-subscribe@qpid.apache.org