By default the oom killer will always target first the biggest process. You'll need to monitor your global memory consumption and check if it is not being eaten by a swarm of little hungry processes.
If artemis is the only significant process sitting on your system, check first the -Xmx value passed to your java runtime and if the running instance have a consumption significantly higher than the configured value. Regards, SL Le 19/09/2022 à 20:36, Ekta Awasthi a écrit : > Hello, > > My apache artemis server running on 2.22.0 is getting randomly, upon checking > it turns out that the OS kernel is killing it with below error. > To my understanding the process with highest consuming memory should be > getting killed but this is NOT the case when I am checking metrics from a > metric tool. The memory and all are well under where it should be and there > are no broker logs to check on anything. > > dmesg | grep "21457" > Out of memory: Kill process 21457 (java) score 852 or sacrifice child > > I am following up with my OS team to see if they can point me in the right > direction or something is off with the version itself...? > > Thanks > Ekta > > CONFIDENTIALITY NOTICE: The information contained in this email and attached > document(s) may contain confidential information that is intended only for > the addressee(s). If you are not the intended recipient, you are hereby > advised that any disclosure, copying, distribution or the taking of any > action in reliance upon the information is prohibited. If you have received > this email in error, please immediately notify the sender and delete it from > your system. >
