You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Felix Ehm (JIRA)" <ji...@apache.org> on 2009/08/03 09:23:35 UTC

[jira] Updated: (AMQ-2339) Enforcing persistent mode for incoming messages

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

Felix Ehm updated AMQ-2339:
---------------------------

    Attachment: ForcePersistencyModeBrokerPlugin.java
                ForcePersistencyModeBroker.java

A new Broker plugin which realizes the requested feature of enforcing persistence mode for incoming messages.

> Enforcing persistent mode for incoming messages
> -----------------------------------------------
>
>                 Key: AMQ-2339
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2339
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.2.0
>            Reporter: Felix Ehm
>            Priority: Minor
>             Fix For: 5.4.0
>
>         Attachments: ForcePersistencyModeBroker.java, ForcePersistencyModeBrokerPlugin.java
>
>   Original Estimate: 2 hours
>  Remaining Estimate: 2 hours
>
> It would be valuable to have a possibility to enforce the persistence mode for incoming messages from clients.
> In our case, one client connected and sent persistent messages with  TTL=0 to a queue without having a consuming client. This caused the broker to  pile up the messages until it died due to missing space (disk & mem). 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.