[
https://issues.apache.org/jira/browse/QPID-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699736#action_12699736
]
Rajith Attapattu commented on QPID-1677:
----------------------------------------
I understand that in 0-8/0-9 you can't do a sync point. But I had it there
thinking about the next AMQP version.
I don't know which way we will go when we add 1.0 support. But since it's only
a small amount of code I just added it anyways.
You would need to have sync publishing for persistent messages if you want to
have script JMS compliance. So this is more a JMS thingy than a version
specific thing.
> 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
> Attachments: QPID_1677.patch
>
>
> 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]
