[
https://issues.apache.org/jira/browse/QPID-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-1106:
-----------------------------------
Affects Version/s: (was: M3)
M4
Fix Version/s: (was: M4)
M5
Arnaud this is not done. IMO as per the JMS spec AUTO_ACK should provide
exactly-once semantics.
Currently AUTO_ACK and DUPS_OK behaves the same.
That is in a clustered environment, when AUTO_ACK is used, there is a
possibility of getting duplicates.
To prevent this I have introduced a System/Connection URLproperty called
sync_ack.
If set to true it will synchronously ack after every message.
However in order for the producer to not replay the messages again (during
failover) and prevent duplicates,we need a way for the JMS client to sync on
every publish as well. To faciliate this, I have introduced a System/Connection
URLproperty called sync_publish={persistent|all} which supercedes
sync_persistent.
(sync_persistent is deprecated but supported for a few releases with a warning
printed if used).
This is covered by QPID-1677
> Make message acknowledgment synchronous
> ---------------------------------------
>
> Key: QPID-1106
> URL: https://issues.apache.org/jira/browse/QPID-1106
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M4
> Reporter: Arnaud Simon
> Assignee: Rajith Attapattu
> Fix For: M5
>
>
> Currently the 0.10 code path does not sync ack of messages. It should be
> configurable so with sync ack we get the at-most-once semantics required by
> JMS with client auto ack mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
