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-1813) [c] Session delivery-id sequence does not allow an arbitrary initial sequence value after reconnect
Date Wed, 02 May 2018 22:21:00 GMT

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

Justin Ross updated PROTON-1813:
--------------------------------
    Summary: [c] Session delivery-id sequence does not allow an arbitrary initial sequence
value after reconnect  (was: Session delivery-id sequence does not allow an arbitrary initial
sequence value after reconnect.)

> [c] Session delivery-id sequence does not allow an arbitrary initial sequence value after
reconnect
> ---------------------------------------------------------------------------------------------------
>
>                 Key: PROTON-1813
>                 URL: https://issues.apache.org/jira/browse/PROTON-1813
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: proton-c-0.21.0
>            Reporter: Chris Morgan
>            Priority: Major
>
> The session->state.incoming_init flag is not reset when the session->state.incoming
delivery map is cleared on reconnect/failover. This causes errors in the transport on incoming
transfer frames when the remote broker begins its delivery-id sequence at a value other then
0. This prevents a broker which begins its delivery-id sequence at 1 to not be able to reconnect. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message