activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elizabeth Keddy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2618) systemUsage tempUsage limit causes broker to lock up when using permanent queue with persistent messages
Date Tue, 23 Nov 2010 14:55:28 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63467#action_63467
] 

Elizabeth Keddy commented on AMQ-2618:
--------------------------------------

Hello,
I'm looking for some suggestions for a workaround.
We are experiencing this problem in 5.4.0 with non-persistent messages.  We see the same stack
trace reported by Simon.

I was experimenting with a solution whereby the temp store usage would be monitored.  Producers
would be blocked before the temp store is filled.
I'm seeing, however, that the temp store usage doesn't drop after the consumer connects and
consumes all messages.  I have left the system running over 12 hours with no new messages
and the temp store usage is remains at  16%.

Any suggests appreciated.
Thanks,
Elizabeth

> 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
>            Assignee: Gary Tully
>             Fix For: 5.5.0
>
>         Attachments: UnlimitedEnqueueTest.java
>
>
> 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.


Mime
View raw message