OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Three node Artemis cluster


This looks wrong to me:

  <connector name="netty-connector">tcp://0.0.0.0:61616</connector>

This is the connector that's referenced in your "artemis-cluster"
cluster-connection which means you're telling other nodes in the cluster
that in order to connect to this node they need to use 0.0.0.0:61616.  Of
course, a remote node using 0.0.0.0:61616 will connect to itself instead
rather than the node broadcasting that information.  Connectors should
almost always use a *real* IP address or hostname.  Try changing that and
seeing how it goes.


Justin

On Mon, Jun 11, 2018 at 1:24 AM, schalmers <
simon.chalmers@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> I'm having some issues with my 3 node Artemis cluster (v2.6.0).
>
> Here is the snippet from my broker.xml on node1:
>
>       <ha-policy>
>         <live-only/>
>       </ha-policy>
>
>
>
>       <connectors>
>          <connector name="netty-connector">tcp://0.0.0.0:61616</connector>
>          <connector
> name="cluster-connector1">tcp://10.0.201.97:61616</connector>
>          <connector
> name="cluster-connector2">tcp://10.0.202.250:61616</connector>
>       </connectors>
>
>
>       <acceptors>
>         <acceptor name="netty-acceptor">tcp://0.0.0.0:61616</acceptor>
>       </acceptors>
>
>
>
>       <cluster-user>someuser</cluster-user>
>       <cluster-password>somepass</cluster-password>
>
>       <cluster-connections>
>          <cluster-connection name="artemis-cluster">
>             <connector-ref>netty-connector</connector-ref>
>             <retry-interval>1000</retry-interval>
>             <use-duplicate-detection>true</use-duplicate-detection>
>             <message-load-balancing>STRICT</message-load-balancing>
>             <max-hops>1</max-hops>
>             <static-connectors>
>                 <connector-ref>cluster-connector1</connector-ref>
>                 <connector-ref>cluster-connector2</connector-ref>
>             </static-connectors>
>          </cluster-connection>
>       </cluster-connections>
>
> The broker.xml is the same on node2 & node3 of the cluster, but I obviously
> change the cluster-connector  URL's in the connectors and static-connectors
> sections to reflect node1/node3 if I'm on node2 and node1/node3 if I'm on
> node3.
>
> When I start the broker on each node, the cluster starts up fine and I can
> see that there are 3 nodes in the cluster logging into the web console for
> each node.
>
> However, if I create an address and a queue on node1, that address and
> queues are not created on any of the other 2 nodes - is that working as
> expected or is something not working correctly?
>
> My assumption reading the documentation is that all queues should be
> available across all 3 nodes of the cluster.
>
>
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>