qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-2847) Use a specific logger and layout for the operational logging
Date Sun, 05 Sep 2010 19:05:32 GMT

    [ https://issues.apache.org/jira/browse/QPID-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906368#action_12906368

Robbie Gemmell commented on QPID-2847:

We recently moved away from using a specific Logger for operational logging to allow more
specific enabling and disabling. Did you mean use a specific Appender? 

With regards to the patch itself: 
Why add the config for Logger org.apache.qpid.server.logging.Log4JMessageLogger when no such
Logger exists? 
Why remove the org.apache.qpid logger config? We use that to control our logger levels as
a whole, independently of the root. 

> Use a specific logger and layout for the operational logging
> ------------------------------------------------------------
>                 Key: QPID-2847
>                 URL: https://issues.apache.org/jira/browse/QPID-2847
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>    Affects Versions: 0.7
>            Reporter: Sorin Suciu
>            Priority: Minor
>             Fix For: 0.7
>         Attachments: qpid-2847.patch
> It is useful the separate the operational logging stream from the regular (via log4j)
mechanism. This allows a user to log the operational messages to a different file (eg for
monitoring purposes) if so desired. 

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

View raw message