You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2021/02/16 16:13:00 UTC
[jira] [Commented] (AMQ-7046) Memory leak in 5.15.5
[ https://issues.apache.org/jira/browse/AMQ-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285311#comment-17285311 ]
Matt Pavlovich commented on AMQ-7046:
-------------------------------------
The AppDynamics screenshot is not sufficient information to troubleshoot. Please test with latest ActiveMQ 5.15.x or 5.16.x and report back.
When reporting, please include a link to a heap dump, the activemq.xml configuration file and infromation about connecting clients-- for example, which protocols and message QOS are being used.
Example
# MQTTv3 QoS 1 with retain messages
# STOMP queues with persistent messages
> Memory leak in 5.15.5
> ---------------------
>
> Key: AMQ-7046
> URL: https://issues.apache.org/jira/browse/AMQ-7046
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.15.5
> Environment: We have a very busy ActiveMQ broker (> 1 million messages per day) running in a docker container on a CentOS VM backed by a MySQL database.
>
> Reporter: James
> Priority: Major
> Labels: memory-leak
> Attachments: Screen Shot 2018-08-31 at 11.23.20.png
>
>
> We have just upgraded to version 5.15.5 in production and have run into a problem which has caused us to roll back to 5.15.4.
> We are seeing a memory leak that the garbage collection cannot cope with and after a few hours the container runs out of memory.
> Attached is a screen shot of our AppDynamics monitoring showing the memory usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)