I can't see one very important point being mentioned and that is non-heap
memory consumption. Does your metric tool cover the entire instance memory
consumption, or is it monitoring just Artemis heap? A rule of thumb is to have
Xmx somewhere around the half of the entire memory available for the
Sad part is I am not seeing any logs with paging or when the broken is getting
killed.
There are simply no logs, the only logs I see are before the process got killed.
Last log I see in Artemis.log is console is up and available. That’s it.
Thanks
Ekta Awasthi,
Engineer, EAI Operations & Suppo
I would recommend check if your system is paging.. and how many
destinations are paging... 2.25.0 offers a significant improvement in
paging.
On Mon, Sep 19, 2022 at 3:31 PM Ekta Awasthi
wrote:
>
> Hello,
>
> Thanks for your response on this issue.
>
> Artemis is the significant process sitting o
Hello,
Thanks for your response on this issue.
Artemis is the significant process sitting on my system with -Xms2G -Xmx6G. At
the time instance was running it was hardly hitting 3gb is what I could see
from monitoring tool so not sure why artemis is getting killed. If any
thoughts, please shar
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 pass
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 m
Ekta, this sounds like an issue worth discussing. However, it doesn't seem
directly related to Michael's question. I recommend you start your own
thread about your issue rather than using this thread. Thanks!
Justin
On Mon, Sep 19, 2022 at 12:53 PM Ekta Awasthi
wrote:
> Hello,
>
> My apache ar
Hey, Michael. This is definitely the right place to seek help. Please
provide details about the crash (e.g. high-level overview of what your
applications are doing, broker configuration, broker logs, etc.) and we'll
see what we can uncover.
Justin
On Mon, Sep 19, 2022 at 12:39 PM Michael Brennoc
Hello,
My apache artemis server running on 2.22.0 is also crashing 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 fr
Good day,
I was hoping to ask some of the more experienced Apache Artemis why my
server keeps crashing after a few hours. I'm running Artemis 2.19.1 on the
default settings on an IBM AIX box. I can provide a copy of the stacktrace,
but it doesn't have much information. I'm also trying to be carefu
Or would you suggest swapping the core bridges for additional broker connections
From: Stephen Baker
Date: Monday, September 19, 2022 at 8:38 AM
To: users@activemq.apache.org
Subject: Re: Dual Mirroring and Core Bridges
To isolate different sets of services they
To isolate different sets of services they run on separate artemis instances,
and to avoid concern spilling into the application layer a limited number of
queues have core bridges to other artemis clusters in the same datacenter for
cross communication.
The dual mirroring on the other hand is f
Sorry, I thought we were already on the same page. Clebert, there was a
workaround for the MySQL bug which was a change to the connection string to not
enable multi-host/replication. I have filed the bug with MySQL Connector/J with
a minimal proof of concept (based on the affected artemis-jdbc c
13 matches
Mail list logo
