Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <931504894.3541266524680097.JavaMail.jira@brutus.apache.org>
Date: Thu, 18 Feb 2010 20:24:40 +0000 (UTC)
From: "Mats Henrikson (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Created: (AMQ-2618) systemUsage tempUsage limit causes
 broker to lock up when using permanent queue with persistent messages
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

systemUsage tempUsage limit causes broker to lock up when using permanent queue with persistent messages
--------------------------------------------------------------------------------------------------------

                 Key: AMQ-2618
                 URL: https://issues.apache.org/activemq/browse/AMQ-2618
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.3.0
            Reporter: Mats Henrikson


It is possible to hang the broker when setting a systemUsage tempUsage limit with permanent queues and persistent messages.

I have attached a test class that demonstrates the problem. I got the test case from AMQ-2610 and have essentially only added the line:
{code}
brokerService.getSystemUsage().getTempUsage().setLimit(10 * 1024 * 1024);
{code}

When that line is in the code the test case hangs after 995 messages, when the line is commented out it runs probably until it runs out of disk space.

When the broker hangs a ctrl+C is not enough to shut it down, when connecting over JMX with JConsole the queue being used in the test will not render its attributes, you can't connect with another consumer or producer etc.

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