Why does the Active MQ broker fails to start when selector has <> based filtering ?

Solution Unverified - Updated -

Issue

  • When activemq.xml contains the following kind of selector then why the broker does not start.
<filteredDestination selector="lastModifiedBy <> 'test migration'" queue="test/input"/>
  • It causes the following kind of error in the amq logs.
Caused by: org.xml.sax.SAXParseException: The value of attribute "selector" associated with an element type "filteredDestination" must not contain the '<' character.

Environment

  • Red Hat JBoss A-MQ
    • 6.1.0

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