It appears mixing ">" and "*" just won't work if "topic.>" matches a
"topic.*" subscription and gets ignored. We will be configuring an
appropriate number of levels to subscribe to and use a "topic.*",
"topic.*.*", topic.*.*.*", etc progression. Unless I'm misunderstanding
something else, this will
Guerrero wrote
>
> Using ActiveMQ 5.5.1.
> ...
> Is there some configuration that I'm missing or is this fixed in 5.6.0, or
> something that just isn't supported?
>
Update: I've upgraded to 5.6.0 and am still seeing this behavior. More
debugging to be done.
--
View this message in context:
> With this default behaviour, N subscriptions on a remote broker look like
> a single subscription to the networked broker.
>
This is something we desire. For instance, A.appId is the central broker,
and A.B.appId, A.B.C.appId, and A.B.D.appId are all connected to A.appId.
When A.B.D.appId se
Maybe you can turning off conduit subscriptions
http://activemq.apache.org/networks-of-brokers.html#NetworksofBrokers-WhentouseandnotuseConduitsubscriptions
Regards
--
Dejan Bosanac
Senior Software Engineer | FuseSource Corp.
dej...@fusesource.com | fusesource.com
skype: dejan.bosanac | twitter:
