As per our IRC conversation, JIRA raised @
https://issues.apache.org/jira/projects/ARTEMIS/issues/ARTEMIS-1928?filter=allopenissues
With regards to the timeout issues, that is caused by the AWS ELB connecting
to the nodes testing they are alive, so please disregard that.
--
Sent from: http://ac
What happens if you actually connect a consumer to node 1 or 2 and try to
consume those messages? I'm not 100% certain what should be visible on the
management console of a node in the cluster when a queue is created on a
different node in the cluster, but I do know with your configuration
message
Changes made:
- Installed and created new brokers using Artemis v2.6.1 from
https://github.com/apache/activemq-artemis/archive/2.6.1.tar.gz and then run
mvn package and used the zip from apache-distribution/target
- Modified broker.xml to fix up the cluster-connector (example broker.xml
attached b
This looks wrong to me:
tcp://0.0.0.0:61616
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:61
I'm having some issues with my 3 node Artemis cluster (v2.6.0).
Here is the snippet from my broker.xml on node1:
tcp://0.0.0.0:61616
tcp://10.0.201.97:61616
tcp://10.0.202.250:61616
tcp://0.0.0.0:61616
