A configurable default channel_max would help a lot! the overwhelming majority of all uses-cases we see use only a handfull of channels anyway.
<br/><br/><br/><br/>On Friday 22 November 2013 at 16:27, Michael Klishin-2 [via RabbitMQ] wrote:
<br/><div class='shrinkable-quote'><br/>>
<br/>> On 22 Nov 2013, at 07:13, carlhoerberg <[hidden email] (/user/SendEmail.jtp?type=node&node=31574&i=0)> wrote:
<br/>>
<br/>> > We would love to be able to define channel_max, for us the default 65536 is
<br/>> > way too high. Some clients are creating thousands of channels, often due to
<br/>> > bugs, and is consuming all available memory.
<br/>>
<br/>>
<br/>> Carl,
<br/>>
<br/>> I did some research and there appears to be at least 3 bugs in our tracker
<br/>> relevant to your request (22844, 22525, 21384).
<br/>>
<br/>> The conclusion seems to be that global channel limit would likely be insufficient. What you
<br/>> really want is per-user limits and/or extra statistics collected by the management plugin to
<br/>> assist you with rogue user detection.
<br/>>
<br/>> Making channel_max default configurable is not hard to do and it may even be possible to
<br/>> get this into a point 3.2.x release. Will this be sufficient for your needs?
<br/>>
<br/>> MK
<br/>>
<br/>> Software Engineer, Pivotal/RabbitMQ
<br/>>
<br/>>
<br/>> _______________________________________________
<br/>> rabbitmq-discuss mailing list
<br/>> [hidden email] (/user/SendEmail.jtp?type=node&node=31574&i=1)
<br/>> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_top" rel="nofollow" link="external">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br/>>
<br/>>
<br/>> If you reply to this email, your message will be added to the discussion below: <a href="http://rabbitmq.1065348.n5.nabble.com/channel-max-tp31572p31574.html" target="_top" rel="nofollow" link="external">http://rabbitmq.1065348.n5.nabble.com/channel-max-tp31572p31574.html</a>
<br/>> To unsubscribe from channel_max, click here (<a href="" target="_top" rel="nofollow" link="external">
<br/>> NAML (<a href="http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" target="_top" rel="nofollow" link="external">http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml</a>)
</div><br/><br/><br/>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://rabbitmq.1065348.n5.nabble.com/channel-max-tp31572p31581.html">Re: channel_max</a><br/>
Sent from the <a href="http://rabbitmq.1065348.n5.nabble.com/">RabbitMQ mailing list archive</a> at Nabble.com.<br/>