You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2015/03/12 17:05:38 UTC
[jira] [Commented] (QPID-2836) Use slf4j rather than log4j on qpid
java broker
[ https://issues.apache.org/jira/browse/QPID-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358868#comment-14358868 ]
Rob Godfrey commented on QPID-2836:
-----------------------------------
Moving the broker to use slf4j rather than log4j directly when logging will ease the transition to moving to a different logging system (e.g. logback) or even just to a newer version of log4j.
There are several pieces of code in the broker which explicitly depend on log4j (e.g. the http LogFileServlet and the JMX plugin LoggingManagementMBean), as well as classes used in starting up the standalone broker. If we are to offer alternative logging providers (rather than just sticking with a single choice, but changing from log4j 1.x to something else) then we would need to make this functionality pluggable in some way.
> Use slf4j rather than log4j on qpid java broker
> -----------------------------------------------
>
> Key: QPID-2836
> URL: https://issues.apache.org/jira/browse/QPID-2836
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.7
> Reporter: Sorin Suciu
> Assignee: Rob Godfrey
> Priority: Minor
> Fix For: 6.0 [Java]
>
>
> The Qpid Java broker uses in lots of places log4j directly. It would be more useful to use slf4j as this would allow more flexibility in terms of logging.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org