You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Jonathan Robie (JIRA)" <qp...@incubator.apache.org> on 2009/10/14 17:12:31 UTC

[jira] Created: (QPID-2140) need similar mechanisms for logging in all clients/brokers

need similar mechanisms for logging in all clients/brokers
----------------------------------------------------------

                 Key: QPID-2140
                 URL: https://issues.apache.org/jira/browse/QPID-2140
             Project: Qpid
          Issue Type: Improvement
          Components: C++ Broker, C++ Client, Dot Net Client, Java Client, Python Client, Ruby Client
            Reporter: Jonathan Robie
             Fix For: 0.6


We need to have similar mechanisms for logging and enabling logging for the broker and all clients. This should include the ability to enable logging without modifying client code, e.g. by using environment variables as we do on the C++ client.

-- 
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


[jira] Updated: (QPID-2140) need similar mechanisms for logging in all clients/brokers

Posted by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marnie McCormack updated QPID-2140:
-----------------------------------

    Fix Version/s:     (was: 0.6)
                   0.7

Moving items unlikely to be completed for 0.6 out to 0.7

> need similar mechanisms for logging in all clients/brokers
> ----------------------------------------------------------
>
>                 Key: QPID-2140
>                 URL: https://issues.apache.org/jira/browse/QPID-2140
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker, C++ Client, Dot Net Client, Java Client, Python Client, Ruby Client
>            Reporter: Jonathan Robie
>             Fix For: 0.7
>
>
> We need to have similar mechanisms for logging and enabling logging for the broker and all clients. This should include the ability to enable logging without modifying client code, e.g. by using environment variables as we do on the C++ client.

-- 
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


[jira] Commented: (QPID-2140) need similar mechanisms for logging in all clients/brokers

Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829582#action_12829582 ] 

Martin Ritchie commented on QPID-2140:
--------------------------------------

Hi Jonathan, I've documented my plans for logging on the Java Broker here:
http://cwiki.apache.org/confluence/display/qpid/Java+Broker+Design+-+Operational+Logging
The current approach allows for easy internationalisation of the messages, whilst providing easy message identification for operation groups. In addition it also provides an easy to use developer interface that has compile time validation of the logging parameters.

Currently I have only implemented the status logging and the design is focused on the broker however it would be good to extend his to the ciient.

It would be great if we could have a consistent logging story across our products.

Whilst I agree it would be nice to enable logging without modify client code. The Java client may also need to be configurable via Log4j as a recent thread on qpid-dev points out when the client is embedded in a application server you can't always set a system property.

As your thinking about logging for the other languages it would be good to get your feedback/views on what I have done for the Java Broker. 

> need similar mechanisms for logging in all clients/brokers
> ----------------------------------------------------------
>
>                 Key: QPID-2140
>                 URL: https://issues.apache.org/jira/browse/QPID-2140
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker, C++ Client, Dot Net Client, Java Client, Python Client, Ruby Client
>            Reporter: Jonathan Robie
>             Fix For: 0.7
>
>
> We need to have similar mechanisms for logging and enabling logging for the broker and all clients. This should include the ability to enable logging without modifying client code, e.g. by using environment variables as we do on the C++ client.

-- 
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