Christopher L. Shannon commented on AMQ-6432:

That error message would only happen during an ack compaction (which is a new 
feature) so I guess the question is what happened that the location couldn't be 
read from the journal file during ack compaction. It is a bit annoying that the 
message form the exception is null so we don't have any idea what is up.  I 
think it would be fine to log the stack trace at the warning level here in case 
it happens again to try and track down the issue.

> 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

Reply via email to