[
https://issues.apache.org/jira/browse/AMQ-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-6432.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.15.0
issue was not related to syncs but doing a scan for acks that could venture
into the newly created data file for the acks.
Adding a limit to the getNextLocation scan provides the necessary restriction
and avoids the EOF and warn.
> Improve 'Failed to load next journal location: null' warning output
> -------------------------------------------------------------------
>
> Key: AMQ-6432
> URL: https://issues.apache.org/jira/browse/AMQ-6432
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.14.0
> Reporter: Martin Lichtin
> Assignee: Gary Tully
> Fix For: 5.15.0
>
>
> Seeing
> {noformat}
> 2016-09-19 15:11:30,270 | WARN | ournal Checkpoint Worker | MessageDatabase
> |
> emq.store.kahadb.MessageDatabase 2104 | 102 -
> org.apache.activemq.activemq-osgi - 5.14.0 |
> Failed to load next journal location: null
> {noformat}
> it'd be great to improve the output in such a case (Journal Checkpoint Worker
> ).
> Why not show the exception stack (it seems weird to only show the stack when
> debug level is enabled).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
