[jira] Updated: (AMQ-1136) Slow consumer causes producer to block on UsageManager.waitForSpace indefinately

["Joe White (JIRA)" <ji...@apache.org>]

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

Joe White updated AMQ-1136:
---------------------------

    Attachment: ActiveMqBrokerThreadDump.txt

I am having the exact issue described by Albert with the UsageManager.waitForSpace. The differences in my system are that I have multiple producers and multiple consumers. It is running in Java 1.5_09 on Red Hat.

The attached file contains a thread dump for the ActiveMq Broker obtained usign 'kill -QUIT [PID]' after the lockup has happened. Each of the transport threads is blockin on UsageManager.waitForSpace.

> Slow consumer causes producer to block on UsageManager.waitForSpace indefinately
> --------------------------------------------------------------------------------
>
>                 Key: AMQ-1136
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1136
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.2.0
>            Reporter: Albert Strasheim
>         Attachments: ActiveMqBrokerThreadDump.txt
>
>
> The issue is described in this thread:
> http://www.nabble.com/Blocking-on-UsageManager.waitForSpace-again-tf3031460.html
> Basically, a slow consumer can cause a producer to block on UsageManager.waitForSpace indefinately.
> A basic code sample to reproduce the problem is provided here:
> http://www.nabble.com/Re%3A-Blocking-on-UsageManager.waitForSpace-again-p8521205.html
> Note that the reproducibility of the bug depends on the initial and maximum size of the VM's heap.

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