[QPID-3252] Regression: broker no longer explicitly flushes messages to store on execution.sync or when sync command bit set.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10
• Fix Version/s: 0.13
• Component/s: C++ Broker
• Assignee: Ken Giusti
• Reporter: Ken Giusti
• Created: 09/May/11 21:10
• Updated: 29/Jul/13 18:53
• Resolved: 05/Aug/11 17:06

Description

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.

Issue Links

• is blocked by: QPID-3394 Broker "leaks" messages that require async completion.