You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/05 16:54:38 UTC

[jira] [Commented] (QPID-5395) [AMQP 1.0] direct proton tracing into qpids own logging

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

ASF subversion and git services commented on QPID-5395:
-------------------------------------------------------

Commit 1548177 from [~gsim] in branch 'qpid/trunk'
[ https://svn.apache.org/r1548177 ]

QPID-5395: use newly added proton tracer callback to unify logging

> [AMQP 1.0] direct proton tracing into qpids own logging
> -------------------------------------------------------
>
>                 Key: QPID-5395
>                 URL: https://issues.apache.org/jira/browse/QPID-5395
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker, C++ Client
>    Affects Versions: 0.26
>            Reporter: Gordon Sim
>            Assignee: Gordon Sim
>             Fix For: 0.27
>
>
> At present protons tracing is entirely distinct from qpidcpp's logging (whether qpidd or qpid:messaging). This means you can't direct the tracing to a file or to syslog. Traces from concurrent connections often get interleaved making them very hard to read.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org