[
https://issues.apache.org/jira/browse/QPID-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604819#comment-13604819
]
Robbie Gemmell commented on QPID-4655:
--------------------------------------
There are some log4j levels set by the broker which anyone using this
functionality to skip the configuration should ensure to set themselves.
Currently, these are:
{noformat}
<logger additivity="true" name="org.apache.qpid">
<level value="warn"/>
</logger>
<!-- Enable info messages for the status-logging hierarchy -->
<logger additivity="true" name="qpid.message">
<level value="info"/>
</logger>
<!-- Subscription state may toggle frequently for clients with low prefetch
so switch off this operational logging by default-->
<logger additivity="true" name="qpid.message.subscription.state">
<level value="off"/>
</logger>
<!-- Enable log messages for the queue notifications -->
<logger additivity="true"
name="org.apache.qpid.server.queue.NotificationCheck">
<level value="info"/>
</logger>
<!-- Set the commons logging that the XML parser uses to WARN, it is very
chatty at debug -->
<logger name="org.apache.commons">
<level value="warn"/>
</logger>
{noformat}
> [Java Broker] add BrokerOptions support to request the Broker not perform
> log4j logging configuration when it is being run embedded
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-4655
> URL: https://issues.apache.org/jira/browse/QPID-4655
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.21
>
>
> The broker configures Log4J at startup due to its heritage of running in a
> standalone VM. We have made the broker easier to run embedded in recent
> times, but it still always configures Log4J at startup. It was requested that
> we enable preventing it from doing this so the embedding application can
> configure things itself.
> Support will be added to the BrokerOptions object to allow requesting the
> Broker instance not perform log4j logging configuration when it is being run
> embedded. This will also prevent the brokers LoggingManagement MBean from
> being initialised, as it is dependant on the logging configuration perfomed
> by the broker and it also has direct support for managing the Log4j
> configuration file which may not exist in this case.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
