ay, January 8, 2025 6:23 PM
> To: users@activemq.apache.org
> Subject: Re: avoiding oom-killer on Artemis
>
> ActiveMQ Artemis uses Netty for just about everything involving the
> network and Netty uses direct memory.
>
> Do you have any JVM on/off heap memor
ssage-
> From: Justin Bertram
> Sent: Wednesday, January 8, 2025 6:23 PM
> To: users@activemq.apache.org
> Subject: Re: avoiding oom-killer on Artemis
>
> ActiveMQ Artemis uses Netty for just about everything involving the
> network and Netty uses direct memory.
>
> D
Message-
From: Justin Bertram
Sent: Wednesday, January 8, 2025 6:23 PM
To: users@activemq.apache.org
Subject: Re: avoiding oom-killer on Artemis
ActiveMQ Artemis uses Netty for just about everything involving the network and
Netty uses direct memory.
Do you have any JVM on/off heap memory
sizes.
>>
>> The main question is where these 0.6GB is coming from if I
>specifically
>> set Artemis heap size to 2G? Is this somekind of direct memory usage
>in the
>> broker? I don't believe that this could be just JVM overhead.
>>
>> --
>> Vilius
>>
&
> Hence my question regarding how to properly calculate Artemis memory sizes.
>>
>> The main question is where these 0.6GB is coming from if I specifically
>> set Artemis heap size to 2G? Is this somekind of direct memory usage in the
>> broker? I don't believe that
is where these 0.6GB is coming from if I specifically
> set Artemis heap size to 2G? Is this somekind of direct memory usage in the
> broker? I don't believe that this could be just JVM overhead.
>
> --
> Vilius
>
> -Original Message-
> From: David Bennion
> S
oming from if I specifically
> set Artemis heap size to 2G? Is this somekind of direct memory usage in the
> broker? I don't believe that this could be just JVM overhead.
>
> --
> Vilius
>
> -Original Message-
> From: David Bennion
> Sent: Wednesday, January 8,
somekind of direct memory usage in the broker?
I don't believe that this could be just JVM overhead.
--
Vilius
-Original Message-
From: David Bennion
Sent: Wednesday, January 8, 2025 4:50 PM
To: users@activemq.apache.org
Subject: Re: avoiding oom-killer on Artemis
OOM Killer ha
OOM Killer happens when Linux determines it doesn't have enough memory to keep
going, so in an act of self preservation it kills a large memory consuming
process rather than crash.
So in your case we can see from the OOM Killer log that in your case you had
2627224kB resident which I think is cl
