[rabbitmq-discuss] Threadpools and rejected messages (java client)

[Jonathan Halterman]

Could messages potentially stack up on the client or will it stop receiving
messages until it has the capacity to process them? My concern is
oversaturating the client/threadpool with messages. Is that possible?

- Jonathan

On Thu, Feb 14, 2013 at 9:54 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> Jonathan,
>
> On 15/02/13 00:29, Jonathan wrote:
>
>> Using the Java client, when a consumer threadpool is maxed out and an
>> attempt to submit work to the threadpool is rejected, what happens to
>> the message? Is it returned to the queue on the server? Is it dropped
>> altogether?
>>
>
> The message gets enqueued at the client side until a thread becomes free.
>
> Matthias.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130214/9b18f6f1/attachment.htm>