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

mKahaDB master slave needs lock when filtered adapter locks are created on the fly

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.8.0
    • Fix Version/s: 5.9.0
    • Component/s: Message Store
    • Labels:
      None

      Description

      <mKahaDB directory="../kahadb">
         <filteredPersistenceAdapters>
            <!-- kahaDB per destinations -->
            <filteredKahaDB perDestination="true" >
              <persistenceAdapter>
                <kahaDB journalMaxFileLength="32mb" />
              </persistenceAdapter>
            </filteredKahaDB>
          </filteredPersistenceAdapters>

      problem:

      1. Starting the slave with an "empty" database, i.e no queues results in the slave trying to start and ultimately failing as the address is in use. There's now lock. Pushing a message to TEST.FOO and then starting the database works OK. The slave comes up and locks and waits.

      2. Now, adding a TEST.FOO1 to the master. The master now has the two queues, TEST.FOO and TEST.FOO1. Kill the master and let the slave take over. The slave only sees TEST.FOO. Not TEST.FOO1.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: