activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6432) Improve 'Failed to load next journal location: null' warning output
Date Thu, 02 Feb 2017 12:14:51 GMT

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

ASF subversion and git services commented on AMQ-6432:
------------------------------------------------------

Commit e3b529129a490d760d21692736e7c0dda7e615e2 in activemq's branch refs/heads/master from
[~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=e3b5291 ]

[AMQ-6432] improve the logging to see the current offset


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

Mime
View raw message