Yes . currently I am creating a connection on each Thrift (similar to HTTP request).�<div><br></div><div><br></div><div>I am assuming each channel is opening a TCP connection - Is it correct ?</div><div>Also should I create a channel from a globale connections instead of creating connection each time?</div>
<div><br></div><div><br clear="all">-Abhishek Kona<br><br>
<br><br><div class="gmail_quote">On Thu, Jul 21, 2011 at 1:12 AM, Michael Klishin <span dir="ltr"><<a href="mailto:michael.s.klishin@gmail.com">michael.s.klishin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">2011/7/20 Abhishek K <span dir="ltr"><<a href="mailto:abhishek.kona@gmail.com" target="_blank">abhishek.kona@gmail.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On each request, I create a new Connection and Channel. During high load times, this is causing the Rabbit to go unresponsive (due to a large no. of open file Descriptor's). <br>
<br>This would be solved if I could connection pool on the client side, what are the strategies and API's suggested for that.</div></blockquote></div><br></div>Why do you need a new connection on each (HTTP?) request? This is what channels are for, if you want to absolutely separate data flowing between on each individual request.<br>
AMQP was designed with the idea of keeping # of TCP connections as low as # of applications.<br clear="all"><font color="#888888"><br>-- <br>MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br>
<a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br><br>
</font></blockquote></div><br></div>