[ https://issues.apache.org/jira/browse/PROTON-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway updated PROTON-1859: -------------------------------- Description: The auto-accept functionality of the messaging_adpater is incorrectly setting the transfer state even if the user had already set it. It is checking for "settled" to decide if it should set state, but this is incorrect on the server side since the message may be locally but not remotely settled at this point. (was: The auto-accept functionality of the MessagingAdapter is incorrectly setting the transfer state even if the user had already set it. It is checking for "settled?" to decide if it should set state, but this is incorrect since the message may be locally but not remotely settled at this point.) > CLONE - [cpp] auto-accept over-writing user transfer state > ---------------------------------------------------------- > > Key: PROTON-1859 > URL: https://issues.apache.org/jira/browse/PROTON-1859 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding > Affects Versions: proton-c-0.23.0 > Reporter: Alan Conway > Assignee: Alan Conway > Priority: Major > Fix For: proton-c-0.24.0 > > > The auto-accept functionality of the messaging_adpater is incorrectly setting > the transfer state even if the user had already set it. It is checking for > "settled" to decide if it should set state, but this is incorrect on the > server side since the message may be locally but not remotely settled at this > point. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org