[
https://issues.apache.org/jira/browse/AMQ-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110438#comment-15110438
]
Gary Tully commented on AMQ-6134:
---------------------------------
please attach your xml config.
the broker should exit. the ioexceptionhandler controls that.
kahadb needs to have checksum enabled so that it can detect journal corruption.
also you can configure pre allocation to force an earlier error.
the disk usage limits are also relevant.
> 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)
