You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2019/01/28 23:33:00 UTC
[jira] [Updated] (PROTON-1998) [Proton-J] Add SASL protocol trace
[ https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated PROTON-1998:
-------------------------------
Summary: [Proton-J] Add SASL protocol trace (was: [Proton-J] Add SASL proton trace)
> [Proton-J] Add SASL protocol trace
> ----------------------------------
>
> Key: PROTON-1998
> URL: https://issues.apache.org/jira/browse/PROTON-1998
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-j
> Reporter: Keith Wall
> Priority: Minor
>
> Unlike Proton, Proton-J does not provide SASL frame trace if environment variable PN_TRACE_FRM is set. It would be useful if Proton-J had this ability too to help diagnose SASL negotiation problem.
> Proton's SASL frame trace looks like this:
> {code:java}
> [0x7fc112c03a00]: -> SASL
> [0x7fc112c03a00]: <- SASL
> [0x7fc112c03a00]:0 <- @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fc112c03a00]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, initial-response=b"guest@Oslo.local"]
> [0x7fc112c03a00]:0 <- @sasl-outcome(68) [code=0]
> [0x7fc112c03a00]: -> AMQP
> [0x7fc112c03a00]:0 -> @open(16) [container-id="be777c26-af6e-4935-a6be-316cc8bbdb35", hostname="127.0.0.1", channel-max=32767]{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org