activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully" <gary.tu...@gmail.com>
Subject Re: Discovery & Store and Forwarding Queues
Date Thu, 15 Jan 2009 18:16:51 GMT
long shot I know, but would the following be relevant:
http://activemq.apache.org/multicast-watch-out-for-ipv6-vs-ipv4-support-on-your-operating-system-or-distribution-or-network.html

2009/1/14 project2501 <darren@ontrenet.com>:
>
> Hi,
>   I read that multicast broker discovery is enabled by default and in my
> 5.2 AMQ it seems its configured that way.
>
> What I want to do is run 2 ActiveMQ 5.2 instances on a subnet, on different
> machines and have them auto-discover each other - and have messages sent to
> any local broker to propagate to other brokers as needed.
>
> To test this, I ran a queue consumer on each broker separately (I'm using
> pyactivemq over activemq-cpp). Each consumer attaches to
> tcp://localhost:port session for the same queue "myqueue". The consumers do
> not know about the other brokers or each other.
>
> I want to send a message to the queue (from any broker) and have either
> consumer receive it - especially when only one is listening.
>
> I couldn't get it to work, but maybe its misconfigured?
>
> I read all the docs on network of brokers, and store-and-forward.
>
> Thanks for any tips!
> --
> View this message in context: http://www.nabble.com/Discovery---Store-and-Forwarding-Queues-tp21466908p21466908.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>



-- 
http://blog.garytully.com

Open Source SOA
http://FUSESource.com

Mime
View raw message