qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Ritchie (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-949) Implement Flow To Disk
Date Thu, 12 Mar 2009 12:24:51 GMT

    [ https://issues.apache.org/jira/browse/QPID-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681286#action_12681286
] 

Martin Ritchie commented on QPID-949:
-------------------------------------

This is where the design for FtD lives:

http://cwiki.apache.org/confluence/display/qpid/Java+Broker+Design+-+Flow+to+Disk

> 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.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Mime
View raw message