[
https://issues.apache.org/jira/browse/QPID-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864055#action_12864055
]
Charles Woerner commented on QPID-2470:
---------------------------------------
I was the original reporter of this problem. Thank you very much for making
this a priority, Kim, I hope I was able to help the project out a bit. I
wonder if there are any plans to backport this to 0.6, or do we need to wait
for 0.7 for the fix?
> Broker does not honour flow-to-disk policy on recovery
> ------------------------------------------------------
>
> Key: QPID-2470
> URL: https://issues.apache.org/jira/browse/QPID-2470
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.7
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> The broker implements a flow-to-disk strategy as a means of retaining message
> content when a queue policy is exceeded. In this strategy, message content
> (whether persistent or transient) is written to the store, then released from
> memory. Before the message may be consumed, the message content must be
> retrieved from the store.
> If a broker is stopped while there is flow-to-disk content containing
> persistent messages, then the broker fails to honour the policy when that
> content is restored. The policy itself is recovered, however, all message
> content is restored, even if it violates that policy. In cases where the
> flow-to-disk content is greater than the available memory, the broker may
> become unresponsive or fail in its recovery owing to memory starvation.
--
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
