As I mentioned, using something like "name#" or "name*" might work for your
use-case technically speaking, but that's relying on undocumented (and
unintended) behavior. I recommend you change to using a delimiter (e.g.
"name.#" or "name.*").
Justin
On Wed, Jun 4, 2025 at 11:54 AM Franck Malka w
I upgraded from 2.14 to 2.41
in 2.14 name# was working fine.
On Wed, Jun 4, 2025 at 7:24 PM Justin Bertram wrote:
> Are you referring to the "match" of an "address-setting"? If so, "name*"
> looks a little strange. As the documentation [1] states:
>
> > An Apache ActiveMQ Artemis wildcard expr
Are you referring to the "match" of an "address-setting"? If so, "name*"
looks a little strange. As the documentation [1] states:
> An Apache ActiveMQ Artemis wildcard expression contains words separated
by a delimiter. The default delimiter is '.' (full stop).
>
> The special characters '#' and '
The Artemis test-suite is full of examples of clustered, embedded brokers.
I'd recommend looking at
org.apache.activemq.artemis.tests.integration.cluster.distribution.SimpleSymmetricClusterTest.
You'll have to dig through some scaffolding for the test-suite, but
everything you need should be there.
I sorted it out by replacing the match prefix from "name#" to "name*"
On Wed, Jun 4, 2025 at 6:59 PM Justin Bertram wrote:
> Can you be more specific about where exactly you're looking? If possible,
> steps to reproduce the behavior you're observing would be ideal.
>
>
> Justin
>
> On Wed, Jun 4
Can you be more specific about where exactly you're looking? If possible,
steps to reproduce the behavior you're observing would be ideal.
Justin
On Wed, Jun 4, 2025 at 4:18 AM Franck Malka wrote:
> Hi, All
>
> In my broker.xml I configured different address-settings for different
> address na
Hello , I hope you are doing well
Could you please assist me with the issue below ?
I am investigating an issue that a client of ours reported but I didn't manage
to figure out the root cause by myself. The application crashes and the event
log shows NullReferenceException in the method Clear
Hi.
We have developed a Spring Boot application with embedded ActiveMQ Artemis
which has MQTT clients. We have our customized `ActiveMQSecurityManager5`
instance which uses the Spring Framework beans to do its thing. Now, we
would like to make it more performant and we are looking at clustering.
Hi, All
In my broker.xml I configured different address-settings for different
address name matches.
mainly altering max-size-bytes and paging-max-size bytes parameters.
I do observe significant improvement in performance with the new settings.
What I don't understand is that on the JMX console i
