[rabbitmq-discuss] Specifying channel_max

Gavin M. Roy gmr at myyearbook.com
Fri Jan 27 16:13:08 GMT 2012

I would look to minimize your channel usage. There is overhead per-channel
on a connection basis. Having run into issues due to unintentionally having
too many channels open recently, I'd offer that if you can use one channel
on one connection instead of two or more channels on one connection, you



On Fri, Jan 27, 2012 at 11:00 AM, Dan Dart <dan at canddi.com> wrote:

> We're after being able to increase channel_max so that Rabbit can
> handle more and not give us errors about not having enough channel
> ids.
> According to Rabbit documentation on AMQP:
> current status in rabbit: planned
> Type: MUST
> Actor: server
> Reference: connection / tune-ok / channel-max / upper-limit
> Text: If the client specifies a channel max that is higher than the
> value provided by the server, the server MUST close the connection
> without attempting a negotiated close. The server may report the error
> in some fashion to assist implementors.
> It would seem the server has to specify this too. But it is not
> implemented in Rabbit right now.
> Am I right? Is there no other way of increasing the load handled and
> getting rid of the channel ids problem?
> We're using this PHP library which specifies channel_max in
> src/main/php/Rabbit/AMQP/Connection.php:69.
> The exception we're getting occurs on line 154 of the same file.
> https://github.com/Canddi/Zend_RabbitMQ
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120127/9fa808f1/attachment.htm>

More information about the rabbitmq-discuss mailing list