qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Stitcher (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-1174) Proton C encodes Open.channel-max 0 as a null and not as a uint.
Date Tue, 23 Jan 2018 21:31:00 GMT

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

Andrew Stitcher commented on PROTON-1174:

[~chug] can you confirm what AMQP lib the receiving app is using here:

As far as I can tell proton-c has a matching bug on receiving an OPEN frame. In other words
it will interpret no channel_max as meaning 0 upon receipt as well as sending.

> Proton C encodes Open.channel-max 0 as a null and not as a uint.
> ----------------------------------------------------------------
>                 Key: PROTON-1174
>                 URL: https://issues.apache.org/jira/browse/PROTON-1174
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.12.0
>            Reporter: Chuck Rolke
>            Assignee: Andrew Stitcher
>            Priority: Major
>              Labels: codec
>             Fix For: proton-c-0.20.0
> A connection Open frame is created with the intent of limiting the peer to exactly one
> {noformat}
>   pn_transport_set_channel_max(pn_trans, 0);
> {noformat}
> Proton encodes the frame with a null 0x40 going over the wire in the channel-max slot.
> A receiving application treats the value as 'default' and uses the spec default value
of 65535. If the receiving application had received a 0x43 (types:encoding uint:uint0) it
would have used the intended channel max of 0.

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