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 <jbert...@apache.org> 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 expression contains words separated
> by a delimiter. The default delimiter is '.' (full stop).
> >
> > The special characters '#' and '*' also have special meaning and can take
> the place of a word.
> >
> > To be clear, the wildcard characters cannot be used like wildcards in a
> regular expression. They operate exclusively on words separated by a
> delimiter.
>
> You should almost certainly be using something like "name.*". Using "name*"
> might work for your use-case technically speaking, but that's relying on
> undocumented (and unintended) behavior.
>
>
> Justin
>
> [1]
>
> https://activemq.apache.org/components/artemis/documentation/latest/wildcard-syntax.html#wildcard-syntax
>
> On Wed, Jun 4, 2025 at 11:04 AM Franck Malka <fma...@modulo.co.il> wrote:
>
> > I sorted it out by replacing the match prefix from "name#" to "name*"
> >
> > On Wed, Jun 4, 2025 at 6:59 PM Justin Bertram <jbert...@apache.org>
> 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, 2025 at 4:18 AM Franck Malka <fma...@modulo.co.il>
> wrote:
> > >
> > > > 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 in the GUI, I
> don't
> > > see
> > > > my new address-settings are reflected there. Any idea what I might be
> > > doing
> > > > wrong?
> > > >
> > > > -Franck.
> > > >
> > >
> >
>

Reply via email to