Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9403EF76F for ; Wed, 3 Apr 2013 21:43:15 +0000 (UTC) Received: (qmail 34002 invoked by uid 500); 3 Apr 2013 21:43:15 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 33915 invoked by uid 500); 3 Apr 2013 21:43:15 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 33906 invoked by uid 99); 3 Apr 2013 21:43:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 21:43:15 +0000 Date: Wed, 3 Apr 2013 21:43:15 +0000 (UTC) From: "Andriy Kalashnykov (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMQ-4434) AcitveMQ stop responding when OS running out of free disk space MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Andriy Kalashnykov created AMQ-4434: --------------------------------------- Summary: AcitveMQ stop responding when OS running out of free disk space Key: AMQ-4434 URL: https://issues.apache.org/jira/browse/AMQ-4434 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: RHEL 6.4 x64 bit Reporter: Andriy Kalashnykov AcitveMQ stop responding when OS running out of free disk space. Steps to reproduce: run ActiveMQ with almost no disk space left, use hdd to the point that there is no more left. This behavior directly affect HA: in my case, i have four instances of ActiveMQ on different physical servers and ActiveMQ configured to share Oracle DB. First server became master worked for a while and went down, then second server (the one with little disk space left) became a master and worked for a while, than it became unresponsive and all AcitveMQ cluster was unaccessible. I belive it's due the fact that on the box with little space ActiveMQ was still running and perhaps preventing DB connection to be release for other servers to use. Suggestion: check disk space on start and periodically after start, once disk space is low on none left - gracefully exit. Regards. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira