Can I configure mKahaDB to support more complex matching

Solution Unverified - Updated -

Issue

The ActiveMQ documentation at http://activemq.apache.org/kahadb.html only gives simple examples of multi(m) kahaDB configurations.

Is it possible to configure mKahaDB to use, for instance, only two KahaDB instances:
- one for queues A and B and topic C
- the other for all the other destinations

This would require the use of something like:

<filteredKahaDB queue="A|B" topic="C">

Does the filteredKahaDB support such complex matching?

Environment

  • Red Hat JBoss A-MQ 6.x
  • Apache ActiveMQ 5.8/5.9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content