[
https://issues.apache.org/jira/browse/AMQ-6831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196869#comment-16196869
]
Gary Tully commented on AMQ-6831:
---------------------------------
[~cshannon] I hope not. I would need to check the journal files to verify the
corrupt locations. A sanity check to see if a current snapshot has the same
determination may help narrow this down.
The logs should indicate the journal locations in question? How do we know
there is no corruption present at the moment?
> Broker fails to start complaining about missing/corrupt journal files after
> upgrading to 5.15.1
> -----------------------------------------------------------------------------------------------
>
> Key: AMQ-6831
> URL: https://issues.apache.org/jira/browse/AMQ-6831
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.15.1
> Reporter: masc
>
> {code}
> 2017-10-09 12:29:36.802 ERROR 4197 --- [pool-3-thread-1]
> org.deku.leoz.node.Application : java.io.IOException: Detected
> missing/corrupt journal files referenced by:[0:ActiveMQ.DLQ] 3 messages
> affected.
> java.lang.Error: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1148)
> ~[na:1.8.0_131]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> ~[na:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_131]
> Caused by: java.io.IOException: Detected missing/corrupt journal files
> referenced by:[0:ActiveMQ.DLQ] 3 messages affected.
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recoverIndex(MessageDatabase.java:965)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase$5.execute(MessageDatabase.java:717)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.recover(MessageDatabase.java:714)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.open(MessageDatabase.java:473)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.load(MessageDatabase.java:493)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.MessageDatabase.doStart(MessageDatabase.java:297)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBStore.doStart(KahaDBStore.java:219)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
> ~[activemq-client-5.15.1.jar:5.15.1]
> at
> org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter.doStart(KahaDBPersistenceAdapter.java:232)
> ~[activemq-kahadb-store-5.15.1.jar:5.15.1]
> {code}
> Downgrading to 5.15.0 resolves the problem.
> This is an embedded broker setup, using
> {code:none}
> val pa = brokerService.persistenceAdapter as KahaDBPersistenceAdapter
> pa.isCheckForCorruptJournalFiles = true
> pa.isIgnoreMissingJournalfiles = false
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
