[
https://issues.apache.org/jira/browse/QPID-8346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051019#comment-17051019
]
Robert Godfrey commented on QPID-8346:
--------------------------------------
I'm still not sure I agree with this
bq. The message should be enqueued after settling the delivery.
The point of receiver settles second is to ensure exactly-once delivery
semantics. If the broker does not enqueue until after the sender settles then
it seems to me you risk the broker failing between the point after the point at
which the sender has settled, believe the message to have been irreversibly
transferred.
I do not see a good reason for the broker to delay the enqueue. The delivery
has occurred - the sender cannot undo this.
> [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: [email protected]
For additional commands, e-mail: [email protected]
