[
https://issues.apache.org/jira/browse/QPID-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327104#comment-16327104
]
ASF subversion and git services commented on QPID-8076:
-------------------------------------------------------
Commit f03f718f98545f15859197f9a1f78f76a985e0a3 in qpid-broker-j's branch
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=f03f718 ]
QPID-8076: [Broker-J] [AMQP 0-9-1] [Publisher Confirms] Delay sending publish
confirms until underlying store transaction completes.
> [0-91] [Publisher Confirms] basic.ack returned to client before message is
> sync'd to disk
> -----------------------------------------------------------------------------------------
>
> Key: QPID-8076
> URL: https://issues.apache.org/jira/browse/QPID-8076
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Affects Versions: 0.32, qpid-java-6.0, qpid-java-broker-7.0.0
> Reporter: Keith Wall
> Priority: Major
>
> QPID-6164 added RabbitMQ's publish confirms [1] feature to Broker-J.
> Concerning when the basic.ack is sent back to the client, the feature
> documentation states:
> {quote}
> h3. When will messages be confirmed?
> ..
> For routable messages, the basic.ack is sent when a message has been accepted
> by all the queues. For persistent messages routed to durable queues, this
> *means persisting to disk*.
> {quote}
> Currently, Broker-J does not behave in this way. The {{basic.ack}} is
> returned to the client before the auto-async transaction has confirmed that
> the data is on disk. The code is AMQChannel#deliverCurrentMessageIfComplete.
> It ought to arrange for the acks to be returned once the sync completes.
>
> [1] [https://www.rabbitmq.com/confirms.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
