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

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

Commit 11ebaccd64db6413abdf3cd60b580e2703df1e8f in activemq's branch 
refs/heads/activemq-5.13.x from [~tmielke]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=11ebacc ]

https://issues.apache.org/jira/browse/AMQ-6071 - Log info about corrupted 
journal records at WARN level

(cherry picked from commit 66c348b1b85e341ed508b9c10028c037a226dfb6)


> Log info about corrupted journal records at WARN level
> ------------------------------------------------------
>
>                 Key: AMQ-6071
>                 URL: https://issues.apache.org/jira/browse/AMQ-6071
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.13.0
>            Reporter: Torsten Mielke
>            Assignee: Gary Tully
>            Priority: Minor
>              Labels: corruption, kahadb
>             Fix For: 5.14.0
>
>
> Currently information about corrupted journal records are logged at INFO 
> level.
> {code}
> 2015-12-03 14:26:21,292 | INFO  | pool-12-thread-1 | Journal  | 
> tore.kahadb.disk.journal.Journal  335 | 171 - 
> org.apache.activemq.activemq-osgi - 5.11.1 | Corrupt journal records found in 
> '/tmp/kahadb/db-1.log' between offsets: 2041..3156
> {code}
> We should change the log level to WARN. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to