You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ken Giusti (JIRA)" <ji...@apache.org> on 2011/08/05 19:07:27 UTC
[jira] [Resolved] (QPID-3252) Regression: broker no longer
explicitly flushes messages to store on execution.sync or when sync command
bit set.
[ https://issues.apache.org/jira/browse/QPID-3252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Giusti resolved QPID-3252.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.11)
0.13
Fix completed with patch to QPID-3394
> Regression: broker no longer explicitly flushes messages to store on execution.sync or when sync command bit set.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: QPID-3252
> URL: https://issues.apache.org/jira/browse/QPID-3252
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.10
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Fix For: 0.13
>
>
> In the previous release of the broker, an execution.sync command, or a message.transfer command with a sync flag would cause the broker to explicitly flush the message(s) and pend until the flushes complete. In the new asynchronous model, the broker does not initiate a flush under these scenarios. Without explicitly flushing, the completion of a message.transfer/execution.sync may delay for an unacceptable amount of time (ex. 1sec+) when used with store.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org