[rabbitmq-discuss] What is a good tradeoff for number of connections and channels/connection for a client ?

Arun Suresh arun.suresh at gmail.com
Thu Jul 22 06:51:21 BST 2010


We are currently using rabbitmq 1.7.2 with the erlang client.
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

We've noticed lately that, we've been seeing a lot of timeouts which is
manifested in the crash reports as follows:

=CRASH REPORT==== 21-Jul-2010::20:14:31 ===
    initial call: amqp_channel:init/1
    pid: <0.26346.57>
    registered_name: []
    exception exit: {timeout,
      in function  gen_server:terminate/6
    ancestors: [<0.686.0>,'q_conn_harley02.ypost.re1.yahoo.com_8',
    messages: [{'EXIT',<0.26348.57>,connection_socket_closed_unexpectedly}]
    links: [<0.26347.57>]
    dictionary: []
    trap_exit: true
    status: running
    heap_size: 1597
    stack_size: 24
    reductions: 1256

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

So I was wondering if you guys have any recommendations wrt to number of
connections and channels/connection to be maintained.
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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100722/93472e66/attachment-0001.htm>

More information about the rabbitmq-discuss mailing list