qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-1970) Improve Operational Logging
Date Sat, 03 Mar 2012 14:47:58 GMT

     [ https://issues.apache.org/jira/browse/QPID-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robbie Gemmell updated QPID-1970:

    Labels: derbystore  (was: )
> Improve Operational Logging
> ---------------------------
>                 Key: QPID-1970
>                 URL: https://issues.apache.org/jira/browse/QPID-1970
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>    Affects Versions: 0.5
>            Reporter: Martin Ritchie
>              Labels: derbystore
>             Fix For: JIRA Cleanup
> Summary:
> The current logging configuration in the Java broker is focused for developers. Logging
is performed on a class basis and as a result it is not easy to enable logging to get an operational
view of the broker. Some work has been done to create configuration files that set the levels
on various classes to provide the operational view of the broker (see Debug using Log4j).
While this provides some good detail it does not provide the full picture.
> Current design work is proceeding here on the wiki:
> http://cwiki.apache.org/confluence/display/qpid/Java+Broker+Design+-+Operational+Logging

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message