Dear Team,
We are using Active MQ artemis with version 2.6.4, we see using Artemis
live-backup mechanism. We are seeing that the messages are getting lost and
duplicated.
Scenario: Power off and On Scenario for HA setup of Artemis
Step-1: Sent 100 messages and power off Node-1
Step2: Automatic fa
So the producer McLighting seems to work after I configured the correct
port. It's messages are visible in the UI, and I created my own
receiver that logs the messages. strange enough I did not see any
errors, but then that is what embedded devices seem to do every now and
then.
Next is to check w
Thank you for the quick response, Justin.
Yes, I am aware of the Pub/Sub model, but not sure where in the
management console I would be supposed to see topics or messages.
What I did not was to create my own Java MQTT client and learned it can
publish to tcp://:1883 rather than tcp://:61613. Also
All the information provided in the ActiveMQ Artemis web console is
expressed in terms of core resources. Since Artemis supports many different
protocols it doesn't make sense to display management information in a
protocol-specific way.
If you want to confirm a message has been sent you can use t
Hi there,
I am trying to connect to MQTT appliances (McLighting and
HomeAssistant) to talk to each other. Knowing about the ASF's software
quality my choice for a MQTT broker resulted in ActiveMQ. I am now
running the vromero/activemq-artemis docker image - so I guess the
setup is valid.
Both McL
On 5/3/19 5:58 AM, Patrick Vansevenant wrote:
I'm not able to send non_persistent messages to an ActiveMQ broker (5.15.3)
with version 0.20.0 or higher of the qpid-jms-client library.
The messages are shown as persistent on the console and they behave also as
persistent.
Sending non_persistent me
I'm not able to send non_persistent messages to an ActiveMQ broker (5.15.3)
with version 0.20.0 or higher of the qpid-jms-client library.
The messages are shown as persistent on the console and they behave also as
persistent.
Sending non_persistent messages with the qpid-jms-client 0.11.1 or lower
Hi All,
I'm using the Websocket connector together with the MQTT connector with the
following settings:
When trying to send larger messages (~ 1MB) from a Websocket client, the
client disconnects. I can send the same message from an MQTT client. These
messages are successfully received by the
