activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Burkard <>
Subject Destination wildcard at first path token
Date Tue, 28 Jul 2015 08:55:50 GMT

We prefix all destination names with an environment shortcut, e.g.
test.mycomponent.process, prod.mycomponent.process etc.

To configure special destination demands, I tried to create an environment
agnostic configuration I can distribute on all broker machines like this:

<policyEntry queue="*.mycomponent.process" ...>

BUT that doesn't work.

The config entry seems to be ignored when the wildcard is at the first
position of the path. Wildcards at other positions work fine.

Since I would like to have a "grouped" view of all destinations of an
environment (some brokers host multiple environments, therefore we need
that prefix) it is not an option to move the environment shortname to the

I could of course pack the destination configs for ALL environments into
the same configfile. But it's kind of confusing to have destinations
configured that are not hosted on the local broker.

Is there any other trick to solve this?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message