activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Clebert Suconic <clebert.suco...@gmail.com>
Subject Re: Artemis deployment question
Date Fri, 16 Oct 2015 01:09:53 GMT
I couldn't see your picture for some reason...

But if you look at this example, it's exactly the scenario you described:

https://github.com/apache/activemq-artemis/tree/master/examples/features/clustered/clustered-topic


If you get the distribution, and go to
./examples/features/clustered/clustered-topic, you can run the example by:


mvn verify


That will create the two servers under ./target/server0 and
./target/server1 for that examples directory, and then you can play with
its config and the client


If you start the servers manually, you can start the client by using the
noServer profile (It's all on the README I believe).


mvn -PnoServer verify



The example is using UDP but you could easily combine it with the static
example (I believe that's what you tried to do) and it should work nicely.




On Thu, Oct 15, 2015 at 9:02 PM, Kevin Niemann <kevin.niemann@gmail.com>
wrote:

> Hello,
>
> I'm looking into an implementation of ActiveMQ Artemis at my org. I want
> to be sure I can use a JMS client to publish to a topic on any node in the
> below diagram and subscribe from any or all other nodes.
>
> I've not been able to prove this configuration. The bridge works between
> two nodes, but when I add additional nodes it doesn't seem to create more
> bridges as I would expect.
>
> Note that the Core Bridges will be going over the WAN, that's why 4-6
> aren't part of the cluster.
>
> See some of my broker.xml below. Let me know if you have questions.
> [image: Inline image 1]
> *Node 1:*
>       <queues>
>          <queue name="jms.topic.Node1">
>             <address>jms.topic.Node1.#</address>
>          </queue>
>       </queues>
>
>       <connectors>
>                   <!-- Connector to the other node -->
>          <connector name="Node4-connector">tcp://192.168.1.5:61616
> </connector>
>          <connector name="Node5-connector">tcp://192.168.1.6:61616
> </connector>
>          <connector name="netty-connector">tcp://192.168.1.2:61616
> </connector>
>       </connectors>
>
>       <bridges>
>          <bridge name="my-bridge">
>             <queue-name>jms.topic.CHQ</queue-name>
>             <retry-interval>1000</retry-interval>
>
>             <retry-interval-multiplier>1.0</retry-interval-multiplier>
>             <initial-connect-attempts>-1</initial-connect-attempts>
>             <reconnect-attempts>-1</reconnect-attempts>
>
> <failover-on-server-shutdown>false</failover-on-server-shutdown>
>             <use-duplicate-detection>true</use-duplicate-detection>
>             <confirmation-window-size>10000000</confirmation-window-size>
>             <static-connectors>
>                <connector-ref>Node4-connector</connector-ref>
>                <connector-ref>Node5-connector</connector-ref>
>             </static-connectors>
>          </bridge>
>       </bridges>
>
> *Node 5:*
>
>       <queues>
>          <queue name="jms.topic.Node5">
>             <address>jms.topic.Node5.#</address>
>          </queue>
>       </queues>
>
>       <connectors>
>                            <!-- Connector to the other node -->
>          <connector name="Node1-connector">tcp://192.168.1.2:61616
> </connector>
>          <connector name="Node2-connector">tcp://192.168.1.3:61616
> </connector>
>          <connector name="Node3-connector">tcp://192.168.1.4:61616
> </connector>
>          <connector name="Node4-connector">tcp://192.168.1.5:61616
> </connector>
>          <connector name="netty-connector">tcp://192.168.1.6:61616
> </connector>
>       </connectors>
>
>       <bridges>
>          <bridge name="my-bridge">
>             <queue-name>jms.topic.Node5</queue-name>
>             <retry-interval>1000</retry-interval>
>             <retry-interval-multiplier>1.0</retry-interval-multiplier>
>             <initial-connect-attempts>-1</initial-connect-attempts>
>             <reconnect-attempts>-1</reconnect-attempts>
>
> <failover-on-server-shutdown>false</failover-on-server-shutdown>
>             <use-duplicate-detection>true</use-duplicate-detection>
>
>             <static-connectors>
>                <connector-ref>Node1-connector</connector-ref>
>                <connector-ref>Node2-connector</connector-ref>
>                <connector-ref>Node3-connector</connector-ref>
>                <connector-ref>Node4-connector</connector-ref>
>             </static-connectors>
>          </bridge>
>       </bridges>
>
> Thanks,
> Kevin
>



-- 
Clebert Suconic

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