[
https://issues.apache.org/jira/browse/AMQ-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110962#comment-15110962
]
Christopher L. Shannon commented on AMQ-6134:
---------------------------------------------
As [~gtully] pointed out, look into using disk usage limits. In version 5.12.0
and later the broker can be configured to periodically check the disk usage and
to shrink the space available if something else external uses up the space.
See AMQ-5393
> ActiveMQ corrupted state when local disk fills up and Queues begin to buffer
> to KahaDB
> --------------------------------------------------------------------------------------
>
> Key: AMQ-6134
> URL: https://issues.apache.org/jira/browse/AMQ-6134
> Project: ActiveMQ
> Issue Type: Bug
> Components: KahaDB
> Affects Versions: 5.11.1
> Reporter: Paul Smith
> Priority: Critical
> Attachments: activemq.log
>
>
> There are already issues reporting this in AMQ-3098 and AMQ-5786 but they
> have been closed as Incomplete, I've left a comment on 5786 but I fear that
> it may get lost.
> Fundamentally KahaDB & ActiveMQ do not survive if Queues start filling up and
> buffering to KahaDB disk when the disk then becomes full because of an
> external issue (in our case rsyslog).
> Because KahaDB does not pre-allocate space, it seems vunerable to this case.
> I will attach broker logs and Kahadb store during the corrupted state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
