activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6432) Improve 'Failed to load next journal location: null' warning output
Date Fri, 03 Feb 2017 17:35:52 GMT

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

Timothy Bish commented on AMQ-6432:
-----------------------------------

Yes, turning off ack compaction will ensure you don't see this warning in you logs. 

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

Mime
View raw message