[
https://issues.apache.org/jira/browse/AMQ-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598723#comment-16598723
]
Christopher L. Shannon commented on AMQ-7046:
---------------------------------------------
The problem is the broker is a complex piece of software with a ton of
components and many different ways it can be used. For example, are you using
topics or queues? what about durables? what protocol are you using? Openwire,
stomp, etc? There's probably hundreds of configurations options that can be
tuned.
The point is with what you have described there is no way to narrow down the
source of the leak. The simplest thing is to provide either a test case (ie
junit or something) or provided a way to reproduce the issue.
> 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: Blocker
> 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
(v7.6.3#76005)
