<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">HI Michael,<br><br>Thanks I will try this out.</div></div><div class="gmail_extra"><br clear="all"><div><font style="font-family:tahoma,sans-serif" face="tahoma, sans-serif">regards,<br>
Loganathan<br>Mob: +91 7760780741 | +91 9944414388<br>Skype: loganathan.sellappa<br></font><span style="font-family:tahoma,sans-serif"><a href="http://vizualize.me/loganathan" target="_blank">ViewMe</a></span><br><br></div>
<br><br><div class="gmail_quote">On Tue, Aug 19, 2014 at 4:15 PM, Michael Klishin <span dir="ltr"><<a href="mailto:mklishin@pivotal.io" target="_blank">mklishin@pivotal.io</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
<br>
On 19 August 2014 at 14:38:37, Loganathan Sellappa (<a href="mailto:loganathan.ms@gmail.com">loganathan.ms@gmail.com</a>) wrote:<br>
> > Thanks is their any patch available for this feature, or is it<br>
> a good way to make connection with one node and switch to other<br>
> one if we get an connection error?<br>
<br>
</div>Like I said before, it is common to use a proxy in front of your cluster<br>
but you can try master:<br>
<br>
<a href="https://github.com/ruby-amqp/bunny/pull/234/files" target="_blank">https://github.com/ruby-amqp/bunny/pull/234/files</a><br>
<a href="https://github.com/ruby-amqp/bunny/commit/091696492de801505943a70320c338ebb63dba30" target="_blank">https://github.com/ruby-amqp/bunny/commit/091696492de801505943a70320c338ebb63dba30</a><br>
<div class="HOEnZb"><div class="h5">--<br>
MK<br>
<br>
Staff Software Engineer, Pivotal/RabbitMQ<br>
</div></div></blockquote></div><br></div>