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

Robbie Gemmell commented on PROTON-1136:
----------------------------------------

I don't think it has been the default for that long comparably (probably since 
0.10), or I'd have expected us to noticed more quickly that it didn't work for 
most things (In looking back I've found issues being raised against the Qpid 
C++ broker, and the Qpid Java broker, and now the servers using proton-j...and 
I don't think any of the released versions currently handle it).

> [proton-j] handle the case when pipelined SASL and OPEN frames are sent for 
> ANONYMOUS login
> -------------------------------------------------------------------------------------------
>
>                 Key: PROTON-1136
>                 URL: https://issues.apache.org/jira/browse/PROTON-1136
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-j
>    Affects Versions: 0.12.0
>            Reporter: Ganesh Murthy
>
> Currently Proton-J is unable to handle pipelined SASL and OPEN frames for 
> ANONYMOUS logins, which are currently sent by proton-c, e.g see the below 
> trace log from Dispatch connecting out using ANONYMOUS:
> {code}
> [0x7f41f80079c0]:  -> SASL
> [0x7f41f80079c0]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, 
> initial-response=b"[email protected]"]
> [0x7f41f80079c0]:  -> AMQP
> [0x7f41f80079c0]:0 -> @open(16) [container-id="Qpid.Dispatch.Router.A", 
> max-frame-size=65536, channel-max=32767, idle-time-out=8000, 
> offered-capabilities=:"ANONYMOUS-RELAY", 
> properties={:product="qpid-dispatch-router", :version="0.6.0"}]
> [0x7f41f80079c0]:  <- SASL
> [0x7f41f80079c0]:0 <- @sasl-mechanisms(64) [sasl-server-mechanisms=:ANONYMOUS]
> [0x7f41f80079c0]:0 <- @sasl-outcome(68) [code=0]
> [0x7f41f80079c0]:  <- AMQP
> {code}
> Given that there are various clients using proton that might do this by 
> default (PROTON-1135 raised regarding that), proton-j should be updated to 
> cope with it.



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

Reply via email to