[
https://issues.apache.org/jira/browse/AMQ-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15525463#comment-15525463
]
Martin Lichtin commented on AMQ-6432:
-------------------------------------
Not seeing the errors all day long, likely just during compaction. We run with
the default for enableJournalDiskSyncs (true).
One observation, it could be that the issue appears when we purge (via the
MBean) and reset stats for all destinations.
> 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.4#6332)
