Improper effective policy configuration when using destination wildcards

Solution Verified - Updated -

Issue

Consider a broker using this policyEntry configuration:

<policyMap>
  <policyEntries>
    <policyEntry queue="DomainA.DomainB.>" prioritizedMessages="false" />
    <policyEntry queue="DomainA.DomainB.*.*.Prioritised.Queue" prioritizedMessages="true" />
  </policyEntries>
</policyMap>

Now a queue named DomainA.DomainB.TestMeA.TestMeB.Prioritized.Queue gets created. One would expect it receives the configuration of the second policyEntry definition. Instead it gets configured for the first policyEntry.
The more specific policy configuration should take effect.

Environment

  • JBoss A-MQ 6.1.1
  • JBoss A-MQ 6.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.