You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by "Claus Ibsen (Updated) (JIRA)" <ji...@apache.org> on 2011/11/07 08:05:51 UTC

[jira] [Updated] (CAMEL-4575) Persistant Dead Letter Channel to avoid memory consumption between retries

     [ https://issues.apache.org/jira/browse/CAMEL-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-4575:
-------------------------------

    Fix Version/s:     (was: 2.8.3)
                       (was: 2.9.0)
                   2.10
    
> Persistant Dead Letter Channel to avoid memory consumption between retries
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-4575
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4575
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Jean-Baptiste Onofré
>             Fix For: 2.10
>
>
> When using a DeadLetterChannel, the messages are stored in memory between the retries (redeliveries). They are flushed from the memory only when we get the maximumRedeliveries value.
> It means that we can have an important memory consumption, because the messages are memory resident for a long time when:
> - if we have an important maximumRedeliveries, especially if we have -1
> - if we have an important redeliveryDelay
> I propose to create a PersistentDeadLetterChannel, working like the DeadLetterChannel, but, between redeliveries, the messages are flushed to a persistent store (filesystem, JMQ queue, JDBC, ...).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira