You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (Jira)" <ji...@apache.org> on 2020/03/03 22:02:00 UTC
[jira] [Commented] (QPID-8346) [Broker-J][AMQP 1.0] Broker
prematurely enqueues unsettled messages with "receiver-settle-mode" set to
"second"
[ https://issues.apache.org/jira/browse/QPID-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050600#comment-17050600 ]
Alex Rudyy commented on QPID-8346:
----------------------------------
[~robbie], [~rgodfrey],
Thanks for pointing out the issue with original JIRA description/title. I have updated the JIRA to reflect your point regarding the state.
> [Broker-J][AMQP 1.0] Broker prematurely enqueues unsettled messages with "receiver-settle-mode" set to "second"
> ---------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8346
> URL: https://issues.apache.org/jira/browse/QPID-8346
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: qpid-java-broker-7.0.1, qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, qpid-java-broker-7.1.4
> Reporter: Alex Rudyy
> Priority: Major
>
> When a sender link attached with {{receiver-settle-mode}} = {{second}} sends not-settled message without using transaction, that message is enqueued immediately into a queue without waiting for the settlement from the sender. It is immediately available for the consumption.
> The message should be enqueued after settling the delivery.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org