qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Ross (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PROTON-1174) Proton C encodes Open.channel-max 0 as a null and not as a uint.
Date Sat, 02 Sep 2017 17:45:00 GMT

     [ https://issues.apache.org/jira/browse/PROTON-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Justin Ross updated PROTON-1174:
--------------------------------
    Fix Version/s:     (was: proton-c-0.18.0)
                   proton-c-0.19.0

> 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
>             Fix For: proton-c-0.19.0
>
>
> A connection Open frame is created with the intent of limiting the peer to exactly one
link.
> {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
(v6.4.14#64029)

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


Mime
View raw message