[rabbitmq-discuss] channel.flow in pyampqlib (was: Re: Erlang has closed?)

mabrek mabrek at gmail.com
Wed Sep 29 10:09:59 BST 2010


On Tue, Sep 28, 2010 at 9:19 PM, Matthias Radestock
<matthias at rabbitmq.com> wrote:
> As others have pointed out, pika may be an option. HOWEVER, since the 2.0.0
> release rabbit is using tcp backpressure to throttle producers, which should
> work with *any* client regardless of whether they support channel.flow. See
> the docs at http://www.rabbitmq.com/extensions.html#memsup

Java client uses blocking IO. It would hang on writing to server that
throttles producers. Dealing with it means starting separate thread by
hands for every connection just to use BlockingQueue.offer with
timeout.

Do you have any plans to switch java client to non-blocking IO (NIO)
and introduce timeouts in content sending methods?

Regards,
Anton Lebedevich.


More information about the rabbitmq-discuss mailing list