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 Wed, 08 Sep 2010 15:28:33 GMT

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

Robbie Gemmell commented on QPID-2847:

I investigated this further it seems we cant use a layout specifically for the operational
logging without having it in a seperate log file from the other logging. Layout can only be
applied to Appenders, and it can be seen when trying the patch that with the two Appenders
using the same file they interfere with each other, and some logging is visibly lost at startup.
Additionally, that is with two normal FileAppenders...if two different RollingAppenders were
used on the same file bad things would likely happen when rolling occured.

I dont think we should have seperate log files, at least not until more of the information
logged off the happy path can be conveyed through the operational logging framework. At present
you need the information from both areas of logging to truly know what is going on and so
seperating the information doesnt seem desirable, only leading to more work to interpret the

In future it would be good to reach a point there would be little need for the other loggers
to be enabled except by developers for debugging during testing and so we could make the default
logger pattern more appropriate for the operational logging. The tests already have a seperate
logging config which we could continue to leverage for all of the log output

> 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
>            Assignee: Robbie Gemmell
>            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