Robbie Gemmell commented on PROTON-961:

I've checked in Gordons suggested fix.

It passes all the existing tests and I verified it fixed the problem by using 
the 'recv' Messenger example against the Java broker, sending it 2MB messages 
from the JMS client followed by small messges from the 'send' Messenger 
example, and checking that the frames on the wire were as expected using a 
protocol trace. As noted earlier, the incoming capacity starvation issue will 
only occur if a local max-frame-size is in effect, and Messenger doesnt do that 
or let you configure it yourself, so the 2MB messages worked fine despite the 
1MB session capacity.

I tried adding a new test and have given up. You cant use Messenger on both 
sides, because it wont fragment sent messages unless a remote max framse size 
is set, and you cant configure it to do that. I then tried using the 
Reactor/Container bits on one side to get the effect, and couldn't see how to 
do what I wanted there either. If someone can point a simple way of doing it 
I'll add one.

> messenger doesn't handle multi-frame transfers
> ----------------------------------------------
>                 Key: PROTON-961
>                 URL: https://issues.apache.org/jira/browse/PROTON-961
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.9.1
>            Reporter: Gordon Sim
>             Fix For: 0.10
> See QPID-6651 for a reproducer.

This message was sent by Atlassian JIRA

Reply via email to