I believe this documentation [1] will answer your question.
Justin
[1]
https://activemq.apache.org/components/artemis/documentation/latest/mqtt.html#automatic-subscription-clean-up
On Thu, Mar 6, 2025 at 3:08 PM Ben Short wrote:
> Can the default expiry interval be changed?
>
> On 06/03/2025
I just tested this on a Windows 10 VM and my custom plugin was loaded as
expected when placed in the instance's lib directory.
Also, you mentioned that the instance folder in 2.39.0 "is rather
different" from 2.30.0, but when I compare the two I only see 2 new files
in the instance directory in 2.
> server.lock becomes the new timestamp when backup takes over.
If the backup is activating that indicates the primary lost the file lock
on server.lock without realizing it (which is a potential issue on NFS).
When the backup activates it updates the timestamp of server.lock and when
the primary
Request for access to the ASF Slack channel.
Artemis amqp(s) wont accept amqps connections.
Not sure if it's PEBCAK or something else.
Tech stack
- Artemis latest
- Three layer ec certificate
- Openjdk 17
- bouncy castle
- AIO
I'm not sure about Kafka, but Apache Pulsar is currently built to support up to
1mm topics. I know that there's active work on using Oxia instead of Zookeeper
for the metadata store with the goal to support hundreds of millions of topics.
That said, millions of topics in Artemis may be a bit of
I'm pretty sure I created it from scratch. The instance folder is rather
different than it was in 2.30.
-Original Message-
From: Justin Bertram
Sent: Wednesday, March 5, 2025 1:10 PM
To: users@activemq.apache.org
Subject: Re: Server plugin for artemis 2.39
*** [Caution] This email is
