[
https://issues.apache.org/jira/browse/AMQ-4434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808939#comment-13808939
]
Claus Ibsen commented on AMQ-4434:
----------------------------------
There is some disk space left check in AMQ 5.9 on startup. You get a WARN
logging if the broker does not have as much free space as configured to allow
to use.
> 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.1#6144)
