[ 
https://issues.apache.org/jira/browse/AMQ-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504268#comment-15504268
 ] 

Martin Lichtin commented on AMQ-6432:
-------------------------------------

Agree with your thinking. A few reoccurences since:
{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
2016-09-19 15:36:32,156 | 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
2016-09-19 16:01:33,572 | 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
2016-09-19 17:08:07,707 | 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}
Something's fishy with the system time on this machine. Could it be a result of 
the time being re-set? Eg. going back in time.

> 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)

Reply via email to