Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
2.18.0
-
None
-
None
-
Artemis mq running as a docker container. The image was built as debian.sh
Consumers are working on .Net Core 3.1 on AMQPNetLite.Core version 2.4
Java info:
openjdk version "1.8.0_302"
OpenJDK Runtime Environment (build 1.8.0_302-b08)
OpenJDK 64-Bit Server VM (build 25.302-b08, mixed mode)Artgument in artemis.profile: -XX:+UseG1GC -XX:+UseStringDeduplication -Xms512M -Xmx2G
Artemis mq running as a docker container. The image was built as debian.sh Consumers are working on .Net Core 3.1 on AMQPNetLite.Core version 2.4 Java info: openjdk version "1.8.0_302" OpenJDK Runtime Environment (build 1.8.0_302-b08) OpenJDK 64-Bit Server VM (build 25.302-b08, mixed mode) Artgument in artemis.profile: -XX:+UseG1GC -XX:+UseStringDeduplication -Xms512M -Xmx2G
Description
In our Docker, swarm Artemis run in a cluster where two nodes are master and two slaves.
The cluster is practically not used, but I have noticed a very rapid increase in RAM consumption on the node to which AMQP consumers are connecting. On the remaining nodes, I did not notice any significant memory consumption. Therefore, I believe that consumers of AMQP messages are causing the problem on the server side. The problem appeared after switching from vromero/activemq-artemis-docker from version 2.15 to 2.18.
