[Bug 1783203] Re: Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment

Andreas Hasenack andreas at canonical.com
Thu Feb 28 13:07:51 UTC 2019


The latest release in the 3.6.x series seems to be 3.6.16. Almost all
releases since 3.6.10 list changes to the management plugin, but I
didn't spot anything obvious. Here are the release notes for each:

https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_16
https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_15
https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_14
https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_13
https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_12
https://github.com/rabbitmq/rabbitmq-server/releases/tag/rabbitmq_v3_6_11

Maybe this in 3.6.12? https://github.com/rabbitmq/rabbitmq-
server/issues/1346

Can anybody more familiar with the problem take a quick peek at the
release notes to see if something about this bug jumps out?


** Bug watch added: github.com/rabbitmq/rabbitmq-server/issues #1346
   https://github.com/rabbitmq/rabbitmq-server/issues/1346

-- 
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1783203

Title:
  Upgrade to RabbitMQ 3.6.10 causes beam lockup in clustered deployment

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1783203/+subscriptions



More information about the Ubuntu-server-bugs mailing list