Hi Luca,
You are seeing the error because you are not setting the correct version
and protocol header in your client. Your client should set:
ProtocolID="MQTT" and ProtocolVersion=4 // 3.1.1
or
ProtocolID="MQlsdp" and ProtocolVersion=3 // 3,1
Artemis will accept both protocol versions (which
The library I am using is this one: https://github.com/evgenido/stomp, from
which I made a very thin client.
The library doesn't seem to be using any feature for failover, so I guess
I'll have to implement it natively.
Still, advices on alternatives are very welcome!
--
View this message in
We are using one 3-node master/slave cluster using level-db in our system.
The requirement is to have reliable message delivery even during fail over.
To test failover, we used a producer that generates 200 AccountIds ( from 0
to 199 ) as the messages, and expected that the consumer would
Hello, I am trying to use the failover mechanism over a C Stomp client. I
understand that clients usually have the feature to establish a connection
to a working broker by sensing the connection status and switching to
another whenever one closes, with something like
Hi,
I tried to setup the mqttjs library and run it in a browser.
Unfortunately, it tries to connect over websocket and artemis cannot
recognize the subprotocol
The source is here: http://pastebin.com/Jgeijbz9
[Thread-10 (activemq-netty-threads-2076099910)] [DEBUG]
We have a number of applications on an application server (Weblogic 11g) and
some of these have MDB's which need to use an additional JMS provider
provided by a remote ActiveMQ v5.9.0. This works fine by populating the JNDI
and adding the ActiveMQ client jars ( activemq-client-5.9.0.jar,
Hi ,
I have a usecase where i am writing a custom plugin and need to expose that
plugin as mbean . For this i am using the spring JMX Mbean exporter API . I
can see my Mbean exposed when i define the bean in activemq.xml file and not
that is part of the activemq plugin.
Here is my activemq.xml
Hi,
I am very new to ActiveMQ. We are in the process of setting up
infrastructure and are looking at a clustered architecture and a shared
drive for persisting messages.We will be looking to start with a two
node(Unix) cluster.
Can you please let me know the best possible configuration for this
