Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-3806

Partial index updates can lead to bogus recovery for the vmcursor of a Q on startup

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.5.1
    • Fix Version/s: 5.6.0
    • Component/s: Broker, Message Store
    • Labels:
      None

      Description

      seeing

       INFO | Using Persistence Adapter: org.apache.activemq.store.kahadb.KahaDBStore@49f10a67
      INFO | KahaDB is version 4
      INFO | Recovering from the journal ...
      INFO | Recovery replayed 1 operations from the journal in 0.063 seconds.
      INFO | ActiveMQ 5.5.1 JMS Message Broker (..) is starting
      INFO | For help or more information please see: http://activemq.apache.org/
      INFO | cursor for queue://JMS/XXXXX has recovered 10000 messages. 2147483647% complete
      INFO | cursor for queue://JMS/XXXXX has recovered 20000 messages. 2147483647% complete

      The crazy % is the result of recovering on a store that has 0 messages. The orderIndex seems to still allow iteration (possibly part of a partial index update) and can result in recovering for ever.

        Attachments

          Activity

            People

            • Assignee:
              gtully Gary Tully
              Reporter:
              gtully Gary Tully
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: