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?<div><br></div>
<div>- Jonathan<br><br><div class="gmail_quote">On Thu, Feb 14, 2013 at 9:54 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jonathan,<br>
<br>
On 15/02/13 00:29, Jonathan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Using the Java client, when a consumer threadpool is maxed out and an<br>
attempt to submit work to the threadpool is rejected, what happens to<br>
the message? Is it returned to the queue on the server? Is it dropped<br>
altogether?<br>
</blockquote>
<br>
The message gets enqueued at the client side until a thread becomes free.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
<br>
</font></span></blockquote></div><br></div>