Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 798D018117 for ; Wed, 20 Jan 2016 14:07:40 +0000 (UTC) Received: (qmail 18510 invoked by uid 500); 20 Jan 2016 14:07:40 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 18450 invoked by uid 500); 20 Jan 2016 14:07:40 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 18427 invoked by uid 500); 20 Jan 2016 14:07:40 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 18421 invoked by uid 99); 20 Jan 2016 14:07:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2016 14:07:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 07C4E2C1F5B for ; Wed, 20 Jan 2016 14:07:40 +0000 (UTC) Date: Wed, 20 Jan 2016 14:07:40 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-8885) None of the users is able to login to cloudstack when RabbitMQ connections are blocked MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-8885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108590#comment-15108590 ] ASF subversion and git services commented on CLOUDSTACK-8885: ------------------------------------------------------------- Commit 0403a3522e2f507bd53f80978c38da026889c743 in cloudstack's branch refs/heads/master from [~remibergsma] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0403a35 ] Merge pull request #857 from karuturi/CLOUDSTACK-8885 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. * pr/857: CLOUDSTACK-8885: added blocked connection listener for rabbitmqeventbus updating rabbitmq amqp client to 3.5.4 from 3.4.2 Signed-off-by: Remi Bergsma > None of the users is able to login to cloudstack when RabbitMQ connections are blocked > -------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-8885 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8885 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: eventbus > Affects Versions: 4.5.2, 4.6.0 > Reporter: Rajani Karuturi > Assignee: Rajani Karuturi > > when the rabbitmq connections are blocked, for example when the 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 and cloudstack becomes unusable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)