[
https://issues.apache.org/activemq/browse/AMQ-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Strachan resolved AMQ-1136.
---------------------------------
Resolution: Fixed
Fix Version/s: 5.0.0
Great stuff; am gonna mark this issue resolved against 5.0.0 unless anyone can
find a reason to reopen it.
Basically one of the big changes in 5.x is the way the broker deals with memory
limits; firstly producers and consumers have separate usage manager limits (on
a per destination basis if required); which eases some of the old lockups we
used to get. Then in addition there's the option of spoling to disk, rather
than blocking indefinitely when a slow consumer is around using message cursors.
http://activemq.apache.org/message-cursors.html
Finally we have a new producer flow control option...
http://activemq.apache.org/producer-flow-control.html
> 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: 5.0.0
> Reporter: Albert Strasheim
> Fix For: 5.0.0
>
> Attachments: ActiveMqBrokerThreadDump.txt, SlowReceive.zip,
> SlowReceive2.zip, SlowReceive3.zip
>
>
> 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.
