You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ulf Lilleengen (JIRA)" <ji...@apache.org> on 2017/10/06 13:32:00 UTC
[jira] [Closed] (DISPATCH-853) Print more information about
transport handle
[ https://issues.apache.org/jira/browse/DISPATCH-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ulf Lilleengen closed DISPATCH-853.
-----------------------------------
Resolution: Won't Fix
This is already available by enabling trace in router log config.
> Print more information about transport handle
> ---------------------------------------------
>
> Key: DISPATCH-853
> URL: https://issues.apache.org/jira/browse/DISPATCH-853
> Project: Qpid Dispatch
> Issue Type: Improvement
> Reporter: Ulf Lilleengen
> Priority: Minor
>
> When debugging connection issues in EnMasse, we found it very useful to enable PN_TRACE_FRM on the router to print the frame trace. However, having multiple connections established at once, it's not clear which connection a given trace belongs to.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org