You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2021/10/11 15:19:00 UTC
[jira] [Updated] (ARTEMIS-3517) Memory leak when using AMQP
[ https://issues.apache.org/jira/browse/ARTEMIS-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-3517:
------------------------------------
Fix Version/s: (was: 2.19.0)
> Memory leak when using AMQP
> ----------------------------
>
> Key: ARTEMIS-3517
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3517
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.18.0
> Environment: 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
>
> {color:#444444}Java info: {color}
> {color:#444444}openjdk version "1.8.0_302"{color}
> {color:#444444}OpenJDK Runtime Environment (build 1.8.0_302-b08){color}
> {color:#444444}OpenJDK 64-Bit Server VM (build 25.302-b08, mixed mode){color}
>
> Artgument in artemis.profile: -XX:+UseG1GC -XX:+UseStringDeduplication -Xms512M -Xmx2G
> Reporter: Paweł Trynkiewicz
> Priority: Major
> Attachments: memory_usage.PNG, ques.PNG
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)