activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-2618) systemUsage tempUsage limit causes broker to lock up when using permanent queue with persistent messages
Date Wed, 21 Mar 2012 16:41:41 GMT

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

Timothy Bish closed AMQ-2618.
-----------------------------

    Resolution: Not A Problem
      Assignee: Timothy Bish  (was: Gary Tully)

This is a configuration issue, and can be resolved by using something like: 

{noformat}
        brokerService.getTempDataStore().setJournalMaxFileLength(10 * 1024);

{noformat}

to configure a temp store journal file length less than the configured limit.  The current
trunk brroker will warn you when you make this configuration error.
                
> systemUsage tempUsage limit causes broker to lock up when using permanent queue with
persistent messages
> --------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2618
>                 URL: https://issues.apache.org/jira/browse/AMQ-2618
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>            Reporter: Mats Henrikson
>            Assignee: Timothy Bish
>             Fix For: 5.x
>
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message