GitHub user karuturi opened a pull request:
https://github.com/apache/cloudstack/pull/857
Cloudstack-8885 added blocked connection listener for rabbitmqeventbus
When rabbitmq connections are blocked(for example when rabbitmq is
server is out of space), all the cloudstack threads which does any
action and publishes to rabbitmq(for example login, launch vm etc.) are
all blocked.
Added a blocked connection listener to handle this and unblock the
parent thread.
also updated rabbitmq amqp client to 3.5.4 from 3.4.2
Testing:
I didnt find a way to write tests for this change as of now.
manually tested that login and other cloudstack apis work when the
configured rabbitmq server goes out of space and publish actions are blocked.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/karuturi/cloudstack CLOUDSTACK-8885
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/857.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #857
----
commit babc60b93a60a88431fd0f3338210f5efb093877
Author: Rajani Karuturi <rajani.karut...@citrix.com>
Date: 2015-09-21T04:45:37Z
updating rabbitmq amqp client to 3.5.4 from 3.4.2
commit 9918f8b121dc3f41d113694e5d373276280e486e
Author: Rajani Karuturi <rajani.karut...@citrix.com>
Date: 2015-09-21T04:57:48Z
CLOUDSTACK-8885: added blocked connection listener for rabbitmqeventbus
When rabbitmq connections are blocked(for example when rabbitmq is
server is out of space), all the cloudstack threads which does any
action and publishes to rabbitmq(for example login, launch vm etc.) are
all blocked.
Added a blocked connection listener to handle this and unblock the
parent thread.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
