This is an automated email from the ASF dual-hosted git repository.
clebertsuconic 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 d3e5b70d90 ARTEMIS-4715 using # wildcard from OpenWire JMS consumer
stopped working
d3e5b70d90 is described below
commit d3e5b70d90f8d21e5e7630c22ae4e14d66fcbea4
Author: Justin Bertram <[email protected]>
AuthorDate: Tue Apr 9 15:03:09 2024 -0500
ARTEMIS-4715 using # wildcard from OpenWire JMS consumer stopped working
---
docs/user-manual/versions.adoc | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/docs/user-manual/versions.adoc b/docs/user-manual/versions.adoc
index 433440b338..82dc79678f 100644
--- a/docs/user-manual/versions.adoc
+++ b/docs/user-manual/versions.adoc
@@ -49,7 +49,7 @@
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&versio
=== Upgrading from 2.32.0
* Due to https://issues.apache.org/jira/browse/ARTEMIS-4532[ARTEMIS-4532] the
names of addresses and queues related to MQTT topics and subscriptions
respectively may change.
-This will only impact you if *both* of the following are true:
+This will impact MQTT use-cases if *both* of the following are true:
+
. The broker is configured to use a xref:wildcard-syntax.adoc[wildcard syntax]
which _doesn't match_ the xref:mqtt.adoc#wildcard-syntax[MQTT wildcard syntax]
(e.g. the default wildcard syntax).
. You are using characters from the broker's wildcard syntax in your MQTT
topic name or filter.
@@ -58,6 +58,13 @@ The dot (`.`) character here is part of the broker's
wildcard syntax, and it is
+
In this case the characters from the broker's wildcard syntax that do not
match the characters in the MQTT wildcard syntax will be escaped with a
backslash (i.e. `\`).
To avoid this conversion you can configure the broker to use the MQTT wildcard
syntax or change the name of the MQTT topic name or filter.
+
++
+This change will also impact OpenWire JMS consumers which are using `\#`
instead of `<` for wildcard purposes.
+In previous versions the `#` character was just passed through when converting
from the OpenWire wildcard format to the Core wildcard format.
+However, now the `\#` character is escaped during conversion.
+It is a bug for an application to use to use `#` as a wildcard with the
OpenWire JMS client; `>` is the proper character to use as specified in the
https://activemq.apache.org/components/classic/documentation/wildcards[ActiveMQ
Classic documentation on wildcards].
+
* Due to https://issues.apache.org/jira/browse/ARTEMIS-4559[ARTEMIS-4559]
folks embedding the broker and also depending on the `artemis-quorum-ri` and/or
`artemis-quorum-api` modules and/or using
`org.apache.activemq.artemis.core.config.ha.DistributedPrimitiveManagerConfiguration`
will need to use `artemis-lockmanager-ri`, `artemis-lockmanager-api`, and
`org.apache.activemq.artemis.core.config.ha.DistributedLockManagerConfiguration`
respectively. Previously these were marked as "experime [...]
== 2.32.0
