This is an automated email from the ASF dual-hosted git repository.
jbertram pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-artemis.git
The following commit(s) were added to refs/heads/main by this push:
new 09643ae453 NO-JIRA update MQTT persistent sub doc
09643ae453 is described below
commit 09643ae4530b2e47c03329262f2a06cee743173a
Author: Justin Bertram <[email protected]>
AuthorDate: Mon Apr 28 09:30:18 2025 -0500
NO-JIRA update MQTT persistent sub doc
---
docs/user-manual/mqtt.adoc | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/docs/user-manual/mqtt.adoc b/docs/user-manual/mqtt.adoc
index 50ec3bfb7d..9e568523aa 100644
--- a/docs/user-manual/mqtt.adoc
+++ b/docs/user-manual/mqtt.adoc
@@ -96,7 +96,7 @@ The information is durable so that MQTT subscribers can
reconnect and resume the
When brokers are configured for high availability this information will be
available on the backup so even in the case of a broker fail-over subscribers
will be able to resume their subscriptions.
While persistent subscriptions can be convenient they impose a performance
penalty since data must be written to storage.
-If you don't need the convenience (e.g. you always use clean sessions) and you
don't want the performance penalty then you can disable it by disabling
durability for the `$sys.mqtt.sessions` queue in `broker.xml`, e.g.:
+If you don't need the convenience (e.g. you always use clean sessions) and/or
you don't want the performance penalty then you can disable it by disabling the
`$sys.mqtt.sessions` queue in `broker.xml`, e.g.:
[,xml]
----
@@ -104,9 +104,7 @@ If you don't need the convenience (e.g. you always use
clean sessions) and you d
...
<address name="$sys.mqtt.sessions">
<anycast>
- <queue name="$sys.mqtt.sessions">
- <durable>false</durable>
- </queue>
+ <queue name="$sys.mqtt.sessions" enabled="false"/>
</anycast>
</address>
...
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
