+++ This bug was initially created as a clone of Bug #452141 +++ In the simplest case we should just issue session exceptions when client attempt to do things that would push the broker above a given limit. --- Additional comment from gsim on 2008-07-10 04:47:51 EDT --- Moving target to 1.1 as we don't yet have a good solution for this. --- Additional comment from gsim on 2008-07-17 11:13:49 EDT --- Initial suggested solution is as follows: On startup broker determines the available system memory. The default policy on any queue for which an explicit policy is not set is to not go above a certain percentage of this (else flow to disk or throw exception as usual). --- Additional comment from gsim on 2008-07-25 09:36:56 EDT --- Fixed by r679462. --- Additional comment from gsim on 2008-08-15 04:03:45 EDT --- Fix involves applying a fixed size (but configurable) default policy for queues (--default-queue-policy). Once the total message data on the queue reaches that limit, further publications will be either flushed to disk (if the queue is durable) or failed.
RHTS test MRG_Messaging/qpid_queue_policy_bz452141_bz456667 proves that queue policies (queue max message count and queue byte size) are implemented and tested. (ON_QA->VERIFIED)
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0867.html