<div dir="ltr">Thank you, Emile. �This is what I expected, but I appreciate the confirmation!<div><br></div><div style>That said, auto-reconnection would be a nice feature enhancement for the Java client. Node-amqp does it and we've found it quite helpful. ;-)</div>
<div><br></div><div style>-Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 2, 2013 at 6:10 AM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Hi Chris,<br>
<div class="im"><br>
On 29/03/13 12:46, Chris wrote:<br>
> Can anyone recommend for or against this library for 3.x deployments?<br>
> �Should we look into it, or should we just plan on implementing the<br>
> reconnection and resubscription logic ourselves?<br>
<br>
</div>The project you refer to has been deprecated. You may decide to re-use<br>
the ideas in it, but the code is no longer maintained and may fail to<br>
compile.<br>
<br>
RabbitMQ has not released a Java client library that contains logic for<br>
reconnecting to HA clusters, but it is simple to do so yourself:<br>
see <a href="http://www.rabbitmq.com/ha.html" target="_blank">http://www.rabbitmq.com/ha.html</a> for details.<br>
<br>
You may also want to look at Spring AMQP which offers some reconnection<br>
support. Another alternative is to front the cluster with a<br>
load-balancing proxy.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
<br>
-Emile<br>
<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>