[rabbitmq-discuss] Problem concurrency isue with rabbitmq (branch bug21673)

scott w scottblanc at gmail.com
Mon Feb 15 20:47:19 GMT 2010


Ok thanks. I will update to tip and also update erlang. You mention all the
channels were blocked. Is there a way to up the # channels?

On Mon, Feb 15, 2010 at 12:41 PM, Matthew Sackman <matthew at lshift.net>wrote:

> Hi Scott,
>
> Thanks for the extra information. There was a bug which I fixed today
> which maybe could have been causing you issues. Please make sure you
> update to the latest on 21673 and do let me know if you see it again.
>
> Of course, it could just be that at that time, all the channels were
> blocked, preventing publishes, due to high memory loads. This can take a
> little while to dealt with, especially in Erlang prior to R13 - the GC
> in R13 is much faster at reclaiming and releasing memory, thus the
> throttling doesn't tend to stay active for as long.
>
> Matthew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100215/111c73bc/attachment.htm 


More information about the rabbitmq-discuss mailing list