Hello group,
we were using ActiveMQ Artemis and it's predecessor HornetQ over years
now but never came to the point where we had to use clustering and ha.
Now this has changed and I have worked through the examples to setup a
ha cluster with 6 nodes (3 live, 3 backup).
While this works like
Steve - there's a lot of detail in there, so I'm not sure if I'm looking at
the right specifics. I don't have a lot of time to dedicate to this right
now.
If short-lived consumers are being used, that is a definite anti-pattern to
solve; ActiveMQ, as with all JMS solutions - and most (all?)
We were able to figure out how to enable the logging within Active MQ
and filtered the logs just for messages pertaining to one queue.
Further to make it simpler to triage we reduced the number of consumers
to 1. From the ActiveMQ logs, we see the consumers are being removed.
Not sure if
Version number in the HTML page title could help too I think:
https://pasteboard.co/X78nH017BiGS.png
--
Vilius
-Original Message-
From: Vilius Šumskas
Sent: Thursday, January 25, 2024 12:26 PM
To: users@activemq.apache.org
Subject: RE: REST Interface for Artemis Broker
I think
I think you should consider adopting
https://developers.google.com/search/blog/2009/02/specify-your-canonical or
similar strategy, so that user search always points to the most up-to-date
documentation.
I've managed to stumble upon old version Artemis docs multiple times myself
(especially on
Just FYI for anyone reading the thread later...
The latest release docs are found at:
https://activemq.apache.org/components/artemis/documentation/
Specifically, the user manual for the latest release (2.31.2 for a few
more days) is found at:
Hi Vaclav,
theoretically, you could use an interceptor[1] to intercept the
CONNECT request and alter the CONNACK response but I would suggest you
contribute[2] by proposing a change to support the optional MQTT feature
3.2.2.3.15 Response Information[3].
[1]
Hi Shiv,
the REST interface was removed in 2.26.0. You can find the original
discussion regarding removal here [1]. The recommended alternative is the
STOMP protocol that is ubiquitous, simple, standardized, and can be used in
almost every circumstance and environment where REST might be used.
