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
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 name matches.
> > mainly altering max-size-bytes and paging-max-size by
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
Ok,
In case the problem is direct memory
Do you think disable netty direct memory would have a serious impact on
performance?
E.g.
-Dio.netty.noPreferDirect=true -Dio.netty.maxDirectMemory=0
-Dio.netty.allocator.type=unpooled
On Thu, Feb 20, 2025 at 10:47 AM Anton Roskvist wrote:
> Hi,
>
> I thi
the problem?
>
>
> Justin
>
> [1] https://github.com/apache/activemq-artemis-native
>
> On Wed, Feb 19, 2025 at 5:35 AM Franck Malka wrote:
>
> > Hi, all
> >
> > I have a case with an Artemis ActiveMq cluster which process a very large
> > number of me
Hi, all
I have a case with an Artemis ActiveMq cluster which process a very large
number of messages per second.
Each few weeks of operation, JVM memory is still cleaning properly but
native memory is not getting cleared.
Did anyone encounter this case?
Does it sounds more like a configuration i
