[
https://issues.apache.org/jira/browse/QPID-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676334#action_12676334
]
Rob Godfrey commented on QPID-1677:
-----------------------------------
The following in the JMS spec certainly implies that send() should be
synchronous in AMQP terms:
"If a failure occurs between the time a client commits its work on a Session and
the commit method returns, the client cannot determine if the transaction was
committed or rolled back. The same ambiguity exists when a failure occurs
between the non-transactional send of a PERSISTENT message and the return
from the sending method."
> Provide the ability to publish synchronously
> --------------------------------------------
>
> Key: QPID-1677
> URL: https://issues.apache.org/jira/browse/QPID-1677
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M4
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: M5
>
>
> 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.
> To faciliate this, I have propose 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).
> In order to provide exactly-once semantics between a single JMS
> publisher-consumer pair (when using AUTO_ACK on the consumer) we need to
> publish synchronously and ack synchronously (QPID-1106).
--
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]
