You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by ripienaar <ri...@devco.net> on 2011/08/08 19:30:08 UTC
networks of brokers, queues and selectors
Hello,
I am having some pain with message delivery for queues with selectors in a
network of 3 brokers.
The broker setup is pretty simple, all duplex links:
monitor1 -> monitor3 -> monitor2
There used to be a monitor2 -> monitor1 link but it causes dupes on topics
so currently disabled. Monitor3 also has a link to another broker but no
subscriptions there so should not matter.
I am using a simple script to test this, 3 connections each with various
subscription using JMS selectors - 1 to each of the brokers with publishing
into monitor3 only. You can see the code @ http://www.pastie.org/2340340
this is just a simple test that exposes the problem.
If I publish into any broker other than monitor3 it all works fine, soon as
I publish into 3 then the consumer on broker2 never get any messages.
I have this same scenario in various combinations on my network. For
example consumer is on monitor1, i publish into monitor3 and TCPDump as well
as the ActiveMQ admin console shows the traffic goes to monitor2 and not
monitor1 as you'd hope eventhough there are no subscribers on monitor2
subscribed with the JMS selector in question.
Any ideas on how to debug this or what more information you might need?
Thanks
--
View this message in context: http://activemq.2283324.n4.nabble.com/networks-of-brokers-queues-and-selectors-tp3727717p3727717.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: networks of brokers, queues and selectors
Posted by ripienaar <ri...@devco.net>.
pol_ice wrote:
>
> I believe you can apply wildcards to policyMap feature:
> http://activemq.apache.org/wildcards.html
>
sure, but I dont believe policy maps let me set the conduit policy on a per
queue basis.
--
View this message in context: http://activemq.2283324.n4.nabble.com/networks-of-brokers-queues-and-selectors-tp3727717p3730453.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: networks of brokers, queues and selectors
Posted by pol_ice <pa...@gmail.com>.
I believe you can apply wildcards to policyMap feature:
http://activemq.apache.org/wildcards.html
just specify it in
<policyEntry queue="*wildcard goes here*" >
or
<policyEntry topic="*wildcard goes here*" >
Is that what you needed?
--
View this message in context: http://activemq.2283324.n4.nabble.com/networks-of-brokers-queues-and-selectors-tp3727717p3730447.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: networks of brokers, queues and selectors
Posted by ripienaar <ri...@devco.net>.
Gary Tully wrote:
>
> introduce more networkconnectors and partition those topics that
> require selectors across them using include and excludes
>
interesting, unfortunate extra complexity but I will give this a try,
thanks!
--
View this message in context: http://activemq.2283324.n4.nabble.com/networks-of-brokers-queues-and-selectors-tp3727717p3730457.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: networks of brokers, queues and selectors
Posted by ripienaar <ri...@devco.net>.
Gary Tully wrote:
>
> introduce more networkconnectors and partition those topics that
> require selectors across them using include and excludes
>
sweet, thanks for the hint, that solved my problem.
--
View this message in context: http://activemq.2283324.n4.nabble.com/networks-of-brokers-queues-and-selectors-tp3727717p3730547.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: networks of brokers, queues and selectors
Posted by Gary Tully <ga...@gmail.com>.
introduce more networkconnectors and partition those topics that
require selectors across them using include and excludes
On 9 August 2011 17:06, ripienaar <ri...@devco.net> wrote:
>
> Gary Tully wrote:
>>
>> http://activemq.apache.org/networks-of-brokers.html#NetworksofBrokers-Conduitsubscriptionsandconsumerselectors
>>
>
> that looks interesting but I use topics quite heavily as well on this
> network and disabling conduit subscriptions causes huge amounts of
> duplication on my network.
>
> Is there a way to use both together? I had a look at the policyMap feature
> as a possible obvious place to look for this but couldnt find any options on
> the per destination policies that could let me do this on a controlled
> manner.
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/networks-of-brokers-queues-and-selectors-tp3727717p3730393.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://fusesource.com
http://blog.garytully.com
Re: networks of brokers, queues and selectors
Posted by ripienaar <ri...@devco.net>.
Gary Tully wrote:
>
> http://activemq.apache.org/networks-of-brokers.html#NetworksofBrokers-Conduitsubscriptionsandconsumerselectors
>
that looks interesting but I use topics quite heavily as well on this
network and disabling conduit subscriptions causes huge amounts of
duplication on my network.
Is there a way to use both together? I had a look at the policyMap feature
as a possible obvious place to look for this but couldnt find any options on
the per destination policies that could let me do this on a controlled
manner.
--
View this message in context: http://activemq.2283324.n4.nabble.com/networks-of-brokers-queues-and-selectors-tp3727717p3730393.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: networks of brokers, queues and selectors
Posted by Gary Tully <ga...@gmail.com>.
http://activemq.apache.org/networks-of-brokers.html#NetworksofBrokers-Conduitsubscriptionsandconsumerselectors
On 8 August 2011 18:30, ripienaar <ri...@devco.net> wrote:
> Hello,
>
> I am having some pain with message delivery for queues with selectors in a
> network of 3 brokers.
>
> The broker setup is pretty simple, all duplex links:
>
> monitor1 -> monitor3 -> monitor2
>
> There used to be a monitor2 -> monitor1 link but it causes dupes on topics
> so currently disabled. Monitor3 also has a link to another broker but no
> subscriptions there so should not matter.
>
> I am using a simple script to test this, 3 connections each with various
> subscription using JMS selectors - 1 to each of the brokers with publishing
> into monitor3 only. You can see the code @ http://www.pastie.org/2340340
> this is just a simple test that exposes the problem.
>
> If I publish into any broker other than monitor3 it all works fine, soon as
> I publish into 3 then the consumer on broker2 never get any messages.
>
> I have this same scenario in various combinations on my network. For
> example consumer is on monitor1, i publish into monitor3 and TCPDump as well
> as the ActiveMQ admin console shows the traffic goes to monitor2 and not
> monitor1 as you'd hope eventhough there are no subscribers on monitor2
> subscribed with the JMS selector in question.
>
> Any ideas on how to debug this or what more information you might need?
> Thanks
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/networks-of-brokers-queues-and-selectors-tp3727717p3727717.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://fusesource.com
http://blog.garytully.com