qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-1809) [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20
Date Tue, 10 Apr 2018 17:54:00 GMT

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

ASF subversion and git services commented on PROTON-1809:

Commit e828055b2a0fade8835cd597e91d0ae3c8bb3f5a in qpid-proton's branch refs/heads/master
from [~aconway]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=e828055 ]

PROTON-1809: PROTON-636: Unable to receive messages when max-frame-size > 2^20

Caused when the frame size was greater than the default session-capacity so the
incoming windows is always 0.


1. No default session-capacity. Session flow control is enabled only if both
   session-capacity and max-frame-size are set. Neither value is deduced

2. Transport error if both are set and session-capacity is less than
   max-frame-size. In this case the incoming window is always 0 so
   communication is impossible.

3. Update API doc for pn_session_set_capacity

4. Add tests to verify this behavior

> [python, ruby] Unable to receive messages when max-frame-size is set to more than 2^20
> --------------------------------------------------------------------------------------
>                 Key: PROTON-1809
>                 URL: https://issues.apache.org/jira/browse/PROTON-1809
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: python-binding, ruby-binding
>    Affects Versions: proton-c-0.22.0
>         Environment: RHEL 7 x86_64
>            Reporter: Radim Kubis
>            Assignee: Alan Conway
>            Priority: Minor
>             Fix For: proton-c-0.23.0
> *Python:*
> {code:java}
>   def on_session_init(self, event):
>      event.transport._set_max_frame_size(VALUE)
> {code}
> 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|https://github.com/rh-messaging/cli-proton-ruby]
> {{cli-proton-ruby-receiver -b <broker> -c <msg_count> --log-msgs dict --conn-max-frame-size
> Receiver is stuck.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message