[ https://issues.apache.org/jira/browse/DISPATCH-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194329#comment-16194329 ]
ASF GitHub Bot commented on DISPATCH-853: ----------------------------------------- GitHub user lulf opened a pull request: https://github.com/apache/qpid-dispatch/pull/207 Print transport handle when accepting a connection See https://issues.apache.org/jira/browse/DISPATCH-853 You can merge this pull request into a Git repository by running: $ git pull https://github.com/lulf/qpid-dispatch DISPATCH-853 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/207.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #207 ---- commit c7af8965c2ba5772669bfe1bb9d8dbbc66429169 Author: Ulf Lilleengen <l...@redhat.com> Date: 2017-10-06T09:11:48Z Print transport handle when accepting a connection ---- > 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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org