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

Andrew Stitcher commented on PROTON-978:
----------------------------------------

As far as I can tell this will happen on the server if the client is 
"pipelining" frames. That is it has sent AMQP header before it actually 
receives the SASL outcome frame.

This is of entire legitimate behaviour, but the buggy behaviour seems bounded 
to this case.

> Framing errors after SASL exchange when max-frame-size is configured
> --------------------------------------------------------------------
>
>                 Key: PROTON-978
>                 URL: https://issues.apache.org/jira/browse/PROTON-978
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.10
>            Reporter: Ted Ross
>            Priority: Blocker
>             Fix For: 0.10
>
>         Attachments: commit-0d2ef9f, commit-34b4c6d
>
>
> Detected in Proton 0.10-RC2
> If the server side of a transport has a non-zero max-frame-size (e.g. 65536), 
> framing errors will occur between the SASL and AMQP sections of the 
> connection protocol because pn_read_frame will read the AMQP header as though 
> it were a frame.



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

Reply via email to