[
https://issues.apache.org/jira/browse/QPID-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marnie McCormack updated QPID-949:
----------------------------------
Fix Version/s: M5
Re Arnaud's comments, I'm not sure that they don't miss the key point of
writing to disk i.e. the movement of data out of VM into somewhere else for
later recovery. I have possibly misunderstood, but commenting to ensure no
confusion.
> Implement Flow To Disk
> ----------------------
>
> Key: QPID-949
> URL: https://issues.apache.org/jira/browse/QPID-949
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Affects Versions: M2.1
> Reporter: Marnie McCormack
> Assignee: Rob Godfrey
> Fix For: M5
>
>
> Currently, the Java Broker can do one of two things with a message it has to
> deliver:
> 1. Keep transient messages in memory until delivered
> 2. Write persistent messages to a message store (like BDB) and keep in memory
> until delivery complete
> This means that the broker is not able to avoid OoM exceptions i.e. send
> enough messages to the broker, especially if your consumers are not active,
> and you could bring the broker done once it explodes its available heap.
> RG to add more details and design proposal here please :-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
