Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-457

KahaDB index corrupted but no errors are reported

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • JBoss A-MQ 6.1
    • JBoss A-MQ 6.0
    • broker
    • None
    • Hide

      1. Use the following config settings:

                          checkpointInterval="5000" 
                    cleanupInterval="5000" 
                    ignoreMissingJournalfiles="true" 
                    checkForCorruptJournalFiles="true" 
                    checksumJournalFiles="true"

      2. Database will be provided separately

      Show
      1. Use the following config settings: checkpointInterval= "5000" cleanupInterval= "5000" ignoreMissingJournalfiles= " true " checkForCorruptJournalFiles= " true " checksumJournalFiles= " true " 2. Database will be provided separately

    Description

      We've discovered a scenario where a broker was restarted. The underlying messages in the broker are not browse-able. There are no errors reported in the log to indicate there is an issue. We can see a recovery was attempted:| 013-11-05 16:15:15,227 | INFO | Recovering from the journal ... | org.apache.activemq.store.kahadb.MessageDatabase | main|

      2013-11-05 16:15:15,228 | INFO | Recovery replayed 1 operations from the journal in 0.071 seconds. | org.apache.activemq.store.kahadb.MessageDatabase | main
      2013-11-05 16:15:15,244 | INFO | ActiveMQ 5.5.1-fuse-03-06 JMS Message Broker (broker01) is starting | org.apache.activemq.broker.BrokerService | main

      The messages are empty (ghost messages as in those from ENTMQ-282 and displayed like the attachment (https://issues.jboss.org/secure/attachment/12368426/DispatchIssue.jpg).Stopping the broker and removing the db.data and db.redo file corrects the problem.| INFO | Recovering from the journal ...|

      INFO | Recovery replayed 37217 operations from the journal in 3.55 seconds.

      Two big concerns here:1. The biggest concern is that there was no indication of a problem outside of digging into the queues
      2. Second is messages were dropped and one may not know if the un-browseable messages had not appeared.

      Attachments

        Activity

          People

            gtully@redhat.com Gary Tully
            rhn-support-sjavurek Susan Javurek
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: