Hello<div><br></div><div>We are currently using rabbitmq 1.7.2 with the erlang client.</div><div>We have some code that sits on top of the erlang client library that abstract away the need for the client to actually know anything about the rabbitmq connections or channels. Basically, we create a pool of connections, and try to multiplex multiple channels across these pooled connections.</div>
<div><br></div><div>We've noticed lately that, we've been seeing a lot of timeouts which is manifested in the crash reports as follows:</div><div><br></div><div><div>=CRASH REPORT==== 21-Jul-2010::20:14:31 ===</div>
<div> crasher:</div><div> initial call: amqp_channel:init/1</div><div> pid: <0.26346.57></div><div> registered_name: []</div><div> exception exit: {timeout,</div><div> {gen_server,call,</div>
<div> [<0.8759.144>,{call,{'channel.open',<<>>}}]}}</div><div> in function gen_server:terminate/6</div><div> ancestors: [<0.686.0>,'q_conn_harley02.ypost.re1.yahoo.com_8',</div>
<div> '<a href="http://q_sup_harley02.ypost.re1.yahoo.com">q_sup_harley02.ypost.re1.yahoo.com</a>',harvester_sup,<0.95.0>]</div><div> messages: [{'EXIT',<0.26348.57>,connection_socket_closed_unexpectedly}]</div>
<div> links: [<0.26347.57>]</div><div> dictionary: []</div><div> trap_exit: true</div><div> status: running</div><div> heap_size: 1597</div><div> stack_size: 24</div><div> reductions: 1256</div>
</div><div><br></div><div>Earlier, prior to us using our abstraction layer, we used have a fixed 10 Channels per connections, and new connections were created every once in a while.. </div><div><br></div><div>So I was wondering if you guys have any recommendations wrt to number of connections and channels/connection to be maintained.</div>
<div>We use rabbitmq as a sort of a router.. around 50000 messages are pushed into the queue per hour. Message size wont exceed a couple of Kb.</div><div><br></div><div>regards</div><div>-Arun</div><div> </div><div> </div>