[
https://issues.apache.org/jira/browse/QPID-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676911#action_12676911
]
Gordon Sim commented on QPID-1692:
----------------------------------
Setting the sync bit will impact performance (at least for durable messages)
and should ideally only be used if the client actually wants to sync on that
specific command. If you just want periodic completion information, use
message.flush.
> Set the sync bit periodically to force the broker to send completions
> ---------------------------------------------------------------------
>
> Key: QPID-1692
> URL: https://issues.apache.org/jira/browse/QPID-1692
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Affects Versions: M4
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Fix For: M5
>
>
> It would be good if the JMS client could periodically set the sync bit to
> force the broker to send completion of commands.
> This would prevent messages being duplicated unnessacerily during a failover
> and also as means to clear it's replay buffer.
> (Note that we also have -Dqpid.session.command_limit and
> -Dqpid.session.byte_limit that will send a sessionFlush whenever one of the
> limits are reached)
--
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:dev-subscr...@qpid.apache.org
