note: the attributes checkForCorruptJournalFiles="true" and checksumJournalFiles="true" must be enabled when the journal files are originally created. In other words. they dont apply retrospectively.
On 6 December 2012 13:44, RJtokenlanring <ing.marco.colo...@gmail.com>wrote: > HI, thank you. > No, this not worked. File is completely corrupted (2KB instead of 32MB as > expected). > What I've expected is the ability to ignore that file and blacklist it. > Should be a good... > > > 2012/12/6 Torsten Mielke-2 [via ActiveMQ] < > ml-node+s2283324n4660269...@n4.nabble.com> > > > Not sure if it helps in your case but can you try deleting the db.data > > index file and restart your broker? It will then rebuild the index based > on > > the journal files. If the journal files are complete bogus though, this > > approach may not help. > > > > > > Regards, > > > > > > Torsten Mielke > > [hidden email] <http://user/SendEmail.jtp?type=node&node=4660269&i=0> > > tmielke.blogspot.com > > > > > > > > On Dec 5, 2012, at 3:36 PM, RJtokenlanring wrote: > > > > > Hi, > > > I've a currupted .log kahadb log file that cause this exception: > > > > > > Failed to start Apache ActiveMQ (localhost, null). Reason: > > > java.io.EOFException > > > java.io.EOFException > > > at java.io.RandomAccessFile.readInt(Unknown Source) > > > ... > > > .. > > > > > > I've configured broker to ignore journalFile as follow: > > > > > > <persistenceAdapter> > > > <kahaDB directory="../kahadb" enableIndexWriteAsync="true" > > > ignoreMissingJournalfiles="true" checkForCorruptJournalFiles="true" > > > checksumJournalFiles="true" /> > > > </persistenceAdapter> > > > > > > Shouldn't also .log files checked? There is a way to automatically drop > > > broken kahadb files? > > > > > > Thank you and regards > > > > > > > > > > > > > > > -- > > > View this message in context: > > > http://activemq.2283324.n4.nabble.com/KahaDB-not-able-to-ignore-broken-log-files-tp4660220.html > > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > > > > > > > > > ------------------------------ > > If you reply to this email, your message will be added to the discussion > > below: > > > > > http://activemq.2283324.n4.nabble.com/KahaDB-not-able-to-ignore-broken-log-files-tp4660220p4660269.html > > To unsubscribe from KahaDB not able to ignore broken log files, click > > here< > http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4660220&code=aW5nLm1hcmNvLmNvbG9tYm9AZ21haWwuY29tfDQ2NjAyMjB8LTE5OTY0ODYxMjg= > > > > . > > NAML< > http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > > -- > Ing. Marco Colombo > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/KahaDB-not-able-to-ignore-broken-log-files-tp4660220p4660274.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://redhat.com http://blog.garytully.com
