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

Andrew Stitcher commented on PROTON-541:
----------------------------------------

My reading of the standard is that each peer tells the other the maximum frame 
size it can accept. So there is no negotiation per se. This implies that the 
frame size is not necessarily symmetrical.

> Problems with multi-frame deliveries
> ------------------------------------
>
>                 Key: PROTON-541
>                 URL: https://issues.apache.org/jira/browse/PROTON-541
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.6
>            Reporter: Ted Ross
>            Assignee: Andrew Stitcher
>
> I made a modification to messenger.c to configure the maximum frame size on 
> transports (there is no API access to this configuration) and then ran a 
> point-to-point test between a sender and a passive receiver using messages 
> larger than the frame max.
> The receiver crashes with the following assertion after several dozen 
> messages are transferred successfully.
>     python: /home/ross/svn/proton/proton-c/src/message/message.c:653: 
> pn_message_decode: Assertion `msg && bytes && size' failed.
> Another observation:
> When the max-frame-size is specified only by one side of the connection, 
> there is no negotiation.  Frames larger than the specified max are 
> transferred.  It is not clear from the specification (2.7.1) whether 
> max-frame-size is intended to be symmetric and apply to transfers in both 
> directions on the connection.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to