activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: Unexpected error on journal read at
Date Wed, 14 Mar 2018 13:03:20 GMT
Can you set checkForCorruptJournalFiles to true (ref:
http://activemq.apache.org/kahadb.html) and see if the broker can recover
gracefully? It's possible that you'd also have to set
ignoreMissingJournalFiles to true.

If that doesn't work, I'm not aware of any tool to skip corrupted messages
or to remove them from a KahaDB data file while leaving the rest of the
file intact, though that would certainly be useful.

If you can afford to lose some messages and to reprocess others, you can
simply delete that one file and enable ignoreMissingJournalFiles, or you
can delete all the KahaDB data files
You'd have to decide whether it was better to reprocess some messages or to
lose all of the unprocessed ones.

You could also submit an enhancement request in JIRA for an administrative
tool that would remove corrupted messages from a data file; it might be
relatively easy for someone to implement.

Tim

On Tue, Mar 13, 2018, 7:49 AM cage <jacek.koziel82@gmail.com> wrote:

> Hello,
> i run activemq 5.15.0 and recently after restart ( i think there might
> appears some kind of fs problem), i get following error:
>
> ERROR | Failed to load message at: 6090:14914228
> java.io.IOException: Unexpected error on journal read at: 6090:14914228
>         at
>
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:28)[activemq-client-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.store.kahadb.KahaDBStore.loadMessage(KahaDBStore.java:1260)[activemq-kahadb-store-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore$4.execute(KahaDBStore.java:594)[activemq-kahadb-store-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.store.kahadb.disk.page.Transaction.execute(Transaction.java:779)[activemq-kahadb-store-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.store.kahadb.KahaDBStore$KahaDBMessageStore.recoverNextMessages(KahaDBStore.java:583)[activemq-kahadb-store-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.store.ProxyMessageStore.recoverNextMessages(ProxyMessageStore.java:110)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.cursors.QueueStorePrefetch.doFillBatch(QueueStorePrefetch.java:127)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor.fillBatch(AbstractStoreCursor.java:448)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.cursors.AbstractStoreCursor.reset(AbstractStoreCursor.java:168)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.cursors.StoreQueueCursor.reset(StoreQueueCursor.java:169)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.Queue.doPageInForDispatch(Queue.java:1976)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.Queue.pageInMessages(Queue.java:2205)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.Queue.doBrowse(Queue.java:1152)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.Queue.expireMessages(Queue.java:932)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.Queue.access$100(Queue.java:106)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.broker.region.Queue$2.run(Queue.java:149)[activemq-broker-5.15.0.jar:5.15.0]
>         at
>
> org.apache.activemq.thread.SchedulerTimerTask.run(SchedulerTimerTask.java:33)[activemq-client-5.15.0.jar:5.15.0]
>         at java.util.TimerThread.mainLoop(Timer.java:555)[:1.8.0_131]
>         at java.util.TimerThread.run(Timer.java:505)[:1.8.0_131]
>  INFO | Stopping BrokerService[localhost] due to exception,
> java.io.IOException: Unexpected error on journal read at: 6090:14914228
>
> this causes the broker to stop, and start every about 30 seconds - forever.
> so it's unusable at the moment.
>
> i the admin console i see the persistent messages on queue
>
>   <http://activemq.2283324.n4.nabble.com/file/t378967/console.png>
>
>
> *Is there any way i can recover or skip the failed messages so the brokers
> runs fine again?*
> Thank you for help
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message