[
https://issues.apache.org/jira/browse/AMQ-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon resolved AMQ-6063.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 5.13.0
Adding a null check allowed the index to continue recovering and for the broker
to restart properly.
> NullPointerException during KahaDB index recovery
> -------------------------------------------------
>
> Key: AMQ-6063
> URL: https://issues.apache.org/jira/browse/AMQ-6063
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.12.1
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.13.0
>
>
> A broker I was testing ran out of disk space the other day when messages were
> being written to it because disk usage checks were not set. After restart,
> the KahaDB index was detected as corrupted but during the recovery a
> NullPointerException occurred.
> The error occurred in MessageDatabase inside recoveryIndex on this line:
> {{sd.locationIndex.remove(tx.keys.location)}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
