We have a Artemis 2.30.0 2 node cluster setup running in amazoncorretto:17 container image (Java 17 JRE), with persistance disabled.
We've had issues with high memory usage for our Artemis broker for a long time, but recently several events raised a possible candidate to the cause. There were sudden drops in address size correlating to container memory drops, and calculations show that each "address size" byte takes 40- 160 "container" bytes. Is this normal and intended? Should the parameter max-size-bytes be multiplied by say 100 to get "actually" container memory usage? The information in this email may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If you are not an intended recipient, you are strictly prohibited from reading, disclosing, distributing, copying or using this email or any of its contents, in any way whatsoever. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message. Please also be advised that emails are not a secure form for communication, and may contain errors.
