ActiveMQ
  1. ActiveMQ
  2. AMQ-3639

Modify MKahaDB To Support Using One Adapter Per Destination Without Explicity Listing Every Desintation In The Configuration

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 5.5.1
    • Fix Version/s: 5.6.0
    • Component/s: Broker
    • Labels:
      None

      Description

      We would like to have the ability to configure MKahaDB to use one adapter per queue without having to explicitly list every queue in our ActiveMQ configuration.

      http://activemq.2283324.n4.nabble.com/MKahaDB-Configure-To-use-One-Adapter-Per-Queue-td4204743.html

        Activity

        Hide
        Gary Tully added a comment -

        addition of boolean attribute perDestination in http://svn.apache.org/viewvc?rev=1231979&view=rev

        So the default match all adapter (when no destination is specified) can implement adapter per destination.

        <filteredKahaDB perDestination="true" >
                <persistenceAdapter>
                  <kahaDB enableJournalDiskSyncs="false"/>
                </persistenceAdapter>
              </filteredKahaDB>
        Show
        Gary Tully added a comment - addition of boolean attribute perDestination in http://svn.apache.org/viewvc?rev=1231979&view=rev So the default match all adapter (when no destination is specified) can implement adapter per destination. <filteredKahaDB perDestination= " true " > <persistenceAdapter> <kahaDB enableJournalDiskSyncs= " false " /> </persistenceAdapter> </filteredKahaDB>

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development