All connections are in blocking state in RabbitMQ in Heroku

[Gennadiy P.]

Hi,

We are using RabbitMQ Bigwig add-on in Heroku. Today we found that all connections are in blocking state.

We tried to purge all queues and delete them, but this didn't help. Then we force closed all connections and restarted the app, but all recreated connections were put in blocking state too.

Could someone recommend an approach we should take to find a reason of this issue and fix it?

[Michael Klishin]

Ask for logs and see if there are any alarms.

Note that you can trigger a RAM alarm by simply having more than a specific number of connections,

depending on node configuration:

http://rabbitmq.com/networking.html

(which is something that you probably cannot control with Heroku but worth mentioning)

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

MK

Staff Software Engineer, Pivotal/RabbitMQ

[Gennadiy P.]

Thank you Michael.

I'm not sure it's possible to get RabbitMQ logs from within Heroku. But, in any case, could you briefly describe what is expected to be done, if there is a memory or disk alarm?

I'm confuse at this point, because now I only have access to a basic Web UI where I can manage connections, channels and queues.

[Michael Klishin]

Please refer to the docs and list archives.

--

You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.