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

Matthew Sackman matthew at lshift.net
Mon Feb 15 20:51:40 GMT 2010

On Mon, Feb 15, 2010 at 12:47:19PM -0800, scott w wrote:
> 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?

Err yes. Make more channels in the client. But the blocking of publishers
is a global thing, in order to stop Rabbit running out of memory, and to
give it a chance to process load. You really have no choice but to sit
it out. I would recommend you try and measure the throughput you're
getting out of your disk drives. There may be some tuning that can be
done there (or just throw more hardware at the problem).


More information about the rabbitmq-discuss mailing list