Re: Artemis 2.0 cluster fail over issue

I believe discovery is still possible using JGroups (e.g. using S3_PING [1] or AWS_PING [2]). Justin [1] http://jgroups.org/manual/index.html#_s3_ping [2] http://jgroups.org/manual/index.html#_aws_ping - Original Message - From: "mtod" To: users@activemq.apache.org Sent: Friday, May 1

Re: Artemis 2.0 cluster fail over issue

Just to close this out I setup static connections and it's failing over fine. I would have preferred to use the discovery but seems that's not possible at this time on AWS. Thanks for your help Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-0-cluster-fa

Re: Artemis 2.0 cluster fail over issue

> To answer your question yes it does support UDP. I was asking about *UDP multicast*. That's not the same as plain UDP. > no it does not support the multicast ip address. Then it does not support UDP multicast since a multicast address (e.g. 231.7.7.7) must be used. Therefore your cluster w

Re: Artemis 2.0 cluster fail over issue

To answer your question yes it does support UDP. But to add no it does not support the multicast ip address. The images shows the inbound and outbound rules broken down by protocol and ip ranges for the AWS image. The outbound has no limits all protocols and all IP's but the inbound shows all prot

Re: Apache Artemis CLI migrate1x

We should maybe include it? On Fri, May 12, 2017 at 11:04 AM Justin Bertram wrote: > It looks to me like you're running the "artemis" command from the instance > directory. You need to run it from the distribution instead. > > > Justin > > - Original Message - > From: "abhijith" > To:

Re: Artemis 2.0 cluster fail over issue

I'm confused. You say, "looks like UDP is allowed," and then you say, "it looks like the 231.7.7.7 would not be able to send." Then you attached some screen shots of what looks like some kind of administration console that I don't recognize. So is UDP multicast supported in your cloud environmen

Re: Artemis 2.0 cluster fail over issue

Hmm I had to verify to configuration looks like UDP is allowed: I'm not an expert on IP but it looks like the 231.7.7.7 would not be able to send out to the server.

Re: Artemis 2.0 cluster fail over issue

Using ${udp-address:231.7.7.7} is functionally equivalent to 231.7.7.7 since both are just details of the overall UDP multicast configuration. You still haven't answered my question about whether or not UDP multicast is supported in your cloud environment. Can you speak to this point? Justin

Re: Artemis 2.0 cluster fail over issue

Looking at the slaves I see an entry in the log for topology I'm not sure what the initialConnectors=[] mean. 12:57:26,528 DEBUG [org.apache.activemq.artemis.core.client.impl.Topology] Topology@4d2d5542[owner=ServerLocatorImpl [initialConnectors=[], discoveryGroupConfiguration=DiscoveryGroupConfig

Re: Artemis 2.0 cluster fail over issue

I just did not have the ${udp-address: } just the ip 231.7.7.7 default from the atremis create function. I just happen to notice that's how they had it in the example to I gave it a try. :) Thanks Mike -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-2-0-clus

Re: Artemis 2.0 cluster fail over issue

So...what were you using for discovery and broadcast when you weren't using UDP multicast? Justin - Original Message - From: "mtod" To: users@activemq.apache.org Sent: Friday, May 12, 2017 11:31:57 AM Subject: Re: Artemis 2.0 cluster fail over issue The UDP multi cast was just added

Re: Artemis 2.0 cluster fail over issue

The UDP multi cast was just added to align the config with the example I tried it both ways. Note: the log in the original post was without that option such as : 231.7.7.7 9876 1 -- View this message in context: http://

RE: How do I Set Up Multiple ActiveMQ Services on one Windows Machine

I forgot to mention that you will need to make sure that your jetty port setting in the "jetty.xml" file are unique per instance ( e.g. instance one 8161 and instance two 8162 ). If you want to isolate the instances then you should consider making the ports for the TransportConnectors and Netwo

Re: Artemis 2.0 cluster fail over issue

> Quick question how does the cluster know when a master fails is the a ping if > so what port does that use? Once the live and backup brokers discover each other they connect to each other via TCP. When that TCP connection breaks the backup essentially knows the live is dead. Your and are

RE: How do I Set Up Multiple ActiveMQ Services on one Windows Machine

Yes I was able to get it working. From the console, execute "activemq create ". So if you want to create a "test" instance in the "/opt" folder on a Linux machine, you would execute "activemq create /opt/test". The "/opt/test/bin" folder will contain a script that has the same name as the in

Re: Artemis 2.0 cluster fail over issue

Thanks for the response. 3 systems running on AWS Windows 2016 I just trimed it down removing any SSL until I can get this working. I followed the https://github.com/apache/activemq-artemis/tree/master/examples/features/ha/replicated-transaction-failover example. Quick question how does the cl

Re: Artemis 2.0 cluster fail over issue

>From what I can see in the log the nodes aren't finding each other and forming >a cluster. What's your configuration? Justin - Original Message - From: "mtod" To: users@activemq.apache.org Sent: Thursday, May 11, 2017 3:44:19 PM Subject: Artemis 2.0 cluster fail over issue I'm tryin

Re: Only last message of a particular topic gets replicated on backup server

I'm not familiar enough with MQTT to say whether or not this is expected. Can you outline specific steps and configuration to reproduce this issue? An automated reproducer (e.g. based on one of the clustering examples shipped in Artemis) would be ideal. Justin - Original Message - Fr

Re: problems with master slave set up artemis 2.0

Can you outline steps and configuration to reproduce what you're seeing? An automated reproducer (e.g. based on one of the clustering examples shipped in Artemis) would be best. Justin - Original Message - From: "Lei" To: users@activemq.apache.org Sent: Wednesday, May 10, 2017 4:18:3

Re: Apache Artemis CLI migrate1x

It looks to me like you're running the "artemis" command from the instance directory. You need to run it from the distribution instead. Justin - Original Message - From: "abhijith" To: users@activemq.apache.org Sent: Friday, May 12, 2017 9:47:34 AM Subject: Apache Artemis CLI migrate1

Apache Artemis CLI migrate1x

I am trying to see if I can use migrate1x command on CLI. But when I run help I do not see that command listed on the cli. Is there any documentation I can take a look? Please let me know if I am missing something here. $ server-master/bin/artemis help usage: artemis [] The most commonly used

Only last message of a particular topic gets replicated on backup server

Hi, I am facing an issue where I have one live and one backup server. I have published two messages on live server for same topic. Now, I stopped live server using ctrl+C and afterwards backup server gets started and becomes active but only last message gets replicated on backup server from live s

Re: ActiveMQ REST Api with HTTP

Hello, Excellent advice: You should be able to publish your messages and then look at them in the web console to confirm that the right values are getting set. I see all my messages in the wed admin console. I see the property test=2 associated with the message.

Re: WARN [org.apache.activemq.broker.TransportConnection.Transport] (qtp906254668-147) Transport Connection to: MQTTSocket_248153872 failed: java.io.IOException: Invalid CONNECT encoding

Finally I attached a debugger to the broker, know I am getting a little bit more information about the problem. Here is what I am getting as WARN : 11:19:16,308 WARN [org.apache.activemq.transport.mqtt.MQTTProtocolConverter] (ActiveMQ Transport: tcp:///192.168.0.116:59362@1884) Exception occurre

Re: WARN [org.apache.activemq.broker.TransportConnection.Transport] (qtp906254668-147) Transport Connection to: MQTTSocket_248153872 failed: java.io.IOException: Invalid CONNECT encoding

Ok understood. I have a A doubt that the warn is comming from the fact that I am connecting a MQTT client over websocket. I don't know if activeMQ allows mqtt+ws. I tried to connect to the port "ws://0.0.0.0:1884" from a mqtt client(apache paho java). Do you have an idea how to enable mqtt over we