You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2017/02/13 18:09:41 UTC

[jira] [Updated] (PROTON-388) Messenger lacks trace/debug logging

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

Robbie Gemmell updated PROTON-388:
----------------------------------
    Component/s:     (was: proton-j)

Removing proton-j component flag, the Messenger API was deprecated in proton-j in the 0.16.0 release (via PROTON-1361) and removed from proton-j in 0.17.0 (via PROTON-1362).

> Messenger lacks trace/debug logging
> -----------------------------------
>
>                 Key: PROTON-388
>                 URL: https://issues.apache.org/jira/browse/PROTON-388
>             Project: Qpid Proton
>          Issue Type: New Feature
>          Components: proton-c
>    Affects Versions: 0.4
>            Reporter: Ken Giusti
>              Labels: messenger
>
> There is no way to gain visibility into Messenger's internal state.  We need the ability to turn on trace logging to allow debugging messenger issues in the field.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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