[
https://issues.apache.org/jira/browse/QPID-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050457#comment-17050457
]
Robbie Gemmell commented on QPID-8346:
--------------------------------------
That was my thinking as I commented, I'd never even considered it as a use
case...but mainly I wanted to note the issue of paying attention to what the
sender might set in the state before enqueing hehe.
> [Broker-J][AMQP 1.0] Broker erronously 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 enqueing should be delayed until receiving disposition settling
> the delivery and the delivery outcome is evaluated to {{Accepted}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
