activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (APLO-70) Add per-destination queue quota
Date Thu, 11 Aug 2011 18:26:31 GMT

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

Hiram Chirino resolved APLO-70.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0-beta5
         Assignee: Hiram Chirino

Added a `quota` attribute to the queue configuration.  This is the space quota the the queue
size is allowed to grow to in terms of disk space.

> Add per-destination queue quota
> -------------------------------
>
>                 Key: APLO-70
>                 URL: https://issues.apache.org/jira/browse/APLO-70
>             Project: ActiveMQ Apollo
>          Issue Type: New Feature
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta5
>
>
> We have to protect our brokers from misbehaving clients. The most
> simple case is a consumer that does not consume the messages in its
> queues (or durable subscriptions), wasting disk space, until it
> affects other clients (disk/partition full).
> Message expiration does help but only really works with constant
> message rates and sizes.
> It would be very good to have per-destinations quotas (at least using
> a message count but a total message size would be useful too) and have
> the broker deleting the oldest not yet consumed messages when needed.
> This way, the queues with quotas would become some kind of rings,
> using limited disk space.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message