<div dir="ltr">Ben, Mathias, Gordon,<br><br>Thanks for your answers.<br><br>The system
around the queue involves a few web servers using php to enqueue
messages at almost every page load and a single java application that
subscribes to the queue and makes one http request to another site for
each message. (To take load off from the web servers and to make their
flow asynchronous, in opposite to when they made the http request
themselves.) The http request usually takes around 50 ms, but sometimes
more and sometimes they fail or timeout after 60 s. We are using a
number of concurrent connections for the http client, not to let a
single http request timing out block the queue. The RabbitMQ subscriber
starts threads that handles the http requests as long as there are
available http connections, if there are no available http connections,
the handleDelivery method waits (while-loop) for a free connection,
thus blocking from receiving more messages until there is time to
handle them.<br>
<br>Currently I acknowledge messages that results in a successful http
request, but any message that fails due to issues outside of our system
(timeouts etc.) does not get acknowledged, since we want them to be
delivered again later.<br>
<br>I am trying not to have any concept of a queue inside of the java
applications since that is the MQs responsibility and to avoid loss of
messages on a crash.<br><br>Since I started this thread I have realized
that it might be smarter to retry with messages that fail due to
timeouts until they succeed instead of throwing them away and wait for
a redelivery.<br>
<br>It is not an issue of load balancing and to do it the way I do it now, basic.reject is probably what I need. <br><br>I'm thankful for, and interested in, any thoughts and ideas.<br><br><div class="gmail_quote">On Thu, Oct 2, 2008 at 11:35 PM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Matthias,<br>
<div class="Ih2E3d"><br>
On Fri, Oct 3, 2008 at 3:25 AM, Matthias Radestock <<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>> wrote:<br>
> I am not at all sure that Basic.Reject is what Jonatan needs.<br>
<br>
</div>Potentially not. I probably left too much of the original context of a<br>
similar question that I answered off list last week. I did ask that<br>
person I they would mind me turning their conversation into a list<br>
topic for the benefit of everybody, but they never did get back to me.<br>
So you and Gordon rightfully point out, it would be better if Jonatan<br>
told us exactly what functionality his application requires.<br>
<br>
Ben<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br></div>