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
To my knowledge, the only jar which should be required is
artemis-jms-client-all.jar as the whole point of this jar is to encapsulate
everything which a JMS client would need. Jetty implementation jars should
definitely not be required to instantiate org.apache.activemq.artemis.
jndi.ActiveMQIniti
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
> Is it possible to have a 3 node cluster with no failover? i.e
live-live-live?
Yes, it is.
Justin
On Sun, Jun 10, 2018 at 10:37 PM, schalmers <
simon.chalm...@manufacturingintelligence.com.au> wrote:
> Hi Justin,
>
> Is it possible to have a 3 node cluster with no failover? i.e
> live-live-l
Thanks Christopher for the migration guide. It wasn't linked in the artemis
user manual. It is a useful resource.
As I mentioned Kerberos support would be a big motivation for an early
migration to Artemis. In the user manual it isn't clear to what extent
Kerberos is supported like it is mentioned
I can answer a few of the questions however I suggest reading the migration
guide and the Artemis documentation as I think a lot of your questions will
be answered in there.
https://activemq.apache.org/artemis/migration/
https://activemq.apache.org/artemis/docs/latest/
1) Artemis supports its own
