[PROTON-1809] [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: proton-c-0.22.0
• Fix Version/s: proton-c-0.23.0
• Component/s: python-binding, ruby-binding
• Environment: RHEL 7 x86_64
• Assignee: Alan Conway
• Reporter: Radim Kubis
• Created: 23/Mar/18 09:05
• Updated: 29/May/18 08:58
• Resolved: 29/May/18 08:58

Description

Python:

  def on_session_init(self, event):
     event.transport._set_max_frame_size(VALUE)

I noticed that the receiver is not able to receive messages when the value for max-frame-size is larger than 2^20 (1048576) bytes (remote_max_frame_size is 4294967295). I'm not really sure if that is expected. This may be reproduced when adding the code above ie.: to simple_recv.py.

Note: This is not a good use case as setting the max-frame-size in on_session_init is really too late. But given that it is too late to set the max-frame-size, I would expect it won't have any effect on the client.

 

Ruby:

From https://github.com/rh-messaging/cli-proton-ruby cli-proton-ruby

cli-proton-ruby-receiver -b <broker> -c <msg_count> --log-msgs dict --conn-max-frame-size 1048577

Receiver is stuck.

Issue Links

• relates to: PROTON-1523 [proton c] API unclear how incoming_capacity and max_frame work
• relates to: PROTON-636 remove confusing default for session capacity and allow disabling it

Sub-Tasks

• [c test] c-connection-driver-tests fail on windows: Closed