[
https://issues.apache.org/jira/browse/AMQ-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849854#comment-15849854
]
Gary Tully commented on AMQ-6432:
---------------------------------
if the trigger is a purge, it may be that the acks are not synced, and doing a
sync write after a purge could sort this.
> 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: Improvement
> Affects Versions: 5.14.0
> Reporter: Martin Lichtin
>
> 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)
