You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2016/01/22 22:41:40 UTC
[jira] [Closed] (AMQ-4434) AcitveMQ stop responding when OS running
out of free disk space
[ https://issues.apache.org/jira/browse/AMQ-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-4434.
-----------------------------
Resolution: Fixed
There has been several enhancements to disk space checks on startup as well as periodic checks to contract or expand the configured limits based on available space. Recommend a retest using the most recent release.
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)