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-52) Support specifying a max limit for the message stores.
Date Sun, 28 Aug 2011 10:23:37 GMT

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

Hiram Chirino resolved APLO-52.
-------------------------------

    Resolution: Invalid

You can now set per queue quotas which should avoid message stores from growing without bound.
 Furthermore, in most systems there are at least a couple of message flows which consume and
produce in one transaction.  In these systems if you hit a global limit like is being requested
in this issue, you will most likely deadlock since messages will no longer be dequeued as
the transaction can no longer enqueue.  setting per destination limits is much less prone
to those deadlock scenarios.

> Support specifying a max limit for the message stores.
> ------------------------------------------------------
>
>                 Key: APLO-52
>                 URL: https://issues.apache.org/jira/browse/APLO-52
>             Project: ActiveMQ Apollo
>          Issue Type: New Feature
>          Components: apollo-bdb, apollo-broker, apollo-jdbm2
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>             Fix For: 1.1
>
>
> Per Massimo Paladin:
> It would allow to limit the application size within the partition and would give
> more control on running different instances or applications in the same partition.

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

        

Mime
View raw message