No subject


Tue Apr 12 10:32:41 BST 2011


explicitly specified

--f46d04426e0cc8982104b87a0b57
Content-Type: text/html; charset=ISO-8859-1

Rabbit: 2.7.1, erlang: R14B03, CentOS, 64bits.<br>We&#39;ve just ran a test with 5 threads querying the API and rabbit is rock solid. So we are looking suspiciously at our load balancer right now. Will report the findings...<br>
<br>Thanks for your help Simon,<br>Vadim.<br><br><div class="gmail_quote">On Wed, Feb 8, 2012 at 9:35 AM, Simon MacMullen <span dir="ltr">&lt;<a href="mailto:simon at rabbitmq.com">simon at rabbitmq.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 08/02/12 17:22, Vadim Chekan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We use http&#39;s &quot;/api/&quot; interface to test for aliveness. Is it a kosher<br>
approach?<br>
</blockquote>
<br></div>
It certainly should be. I recall there was a bug in the aliveness test in some old version - what are you using?<div class="HOEnZb"><div class="h5"><br>
<br>
Cheers, Simon<br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>From RFC 2631: In ASN.1, EXPLICIT tagging is implicit unless IMPLICIT is explicitly specified<br>

--f46d04426e0cc8982104b87a0b57--


More information about the rabbitmq-discuss mailing list