qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-572) Adding log info with proton transport id and related remote IP/port
Date Wed, 23 Nov 2016 18:48:58 GMT

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

ASF GitHub Bot commented on DISPATCH-572:
-----------------------------------------

GitHub user ganeshmurthy opened a pull request:

    https://github.com/apache/qpid-dispatch/pull/116

    DISPATCH-572 - Added fprintf message that associates the transport po…

    …inter to the connector name

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-572

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-dispatch/pull/116.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 #116
    
----
commit fbfe9375a339d4e839e9aca275dd8360a62e74a7
Author: Ganesh Murthy <gmurthy@redhat.com>
Date:   2016-11-23T18:43:30Z

    DISPATCH-572 - Added fprintf message that associates the transport pointer to the connector
name

----


> Adding log info with proton transport id and related remote IP/port
> -------------------------------------------------------------------
>
>                 Key: DISPATCH-572
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-572
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>            Reporter: Paolo Patierno
>            Assignee: Ganesh Murthy
>             Fix For: 0.8.0
>
>
> Hi,
> enabling the Qpid Proton trace through PN_TRACE_FRM=1 when I start the Qpid Dispatch
Router, I need sometimes to know who is the remote peer is exchanging traced messages.
> For example, considering these few lines of trace (running the Qpid Dispatch Router)
:
>  
> Accepted from 127.0.0.1:48192
> Accepted from 127.0.0.1:48190
> [0x7fbc44016390]:  <- SASL
> [0x7fbc44016390]:  -> SASL
> [0x7fbc44003b70]:  <- SASL
> [0x7fbc44003b70]:  -> SASL
> [0x7fbc44016390]:0 -> @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS,
:PLAIN]]
> [0x7fbc44003b70]:0 -> @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS,
:PLAIN]]
>  
> The router accepts two connections from remote clients (we see IP and port) but then
every message is related to an "identifier" (I guess it should be the file descriptor related
to the used socket).
> If I need to match these information with Wireshark (where I can see remote port) I don't
know if remote clients using remote port 48192 is related to 0x7fbc44016390 or 0x7fbc44003b70.
> I think it could be a good information to add into the trace at least showing the "identifier"
after the accepted message, i.e. :
> Accepted from 127.0.0.1:48192 [0x7fbc44016390]
> It's also true, that messages related to something like [0x7fbc44016390] come from Qpid
Proton and messages like "Accepted ..." come from Qpid Dispatch Router.
> Thanks,
> Paolo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message