[
https://issues.apache.org/jira/browse/QPID-7828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068091#comment-16068091
]
Keith Wall commented on QPID-7828:
----------------------------------
As per this conversation, root cause was the Qpid Log4J custom appender
compressing a very large log file in memory. The appender in question is
already been removed from newer Qpid release. Closing at Won't Fix.
https://lists.apache.org/thread.html/76f7b5619160cf5146d64205ed2dabef51d9eba7cc4e718f6cb299db@%3Cdev.qpid.apache.org%3E
> QPid 0.32 is going out of memory
> --------------------------------
>
> Key: QPID-7828
> URL: https://issues.apache.org/jira/browse/QPID-7828
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.32
> Environment: Linux
> Reporter: Akhil Samnotra
> Labels: performance
> Fix For: 0.32
>
> Attachments: image1.PNG, image2.PNG, image3.PNG
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Hi,
> We are using QPID 0.32 version .
> We have observed that the qpid broker is going out of memory and having
> memory leak even though we have increased the heap memory to 3 GB and that
> was observed using MAT TOOl. It was seen that the memory is consumed by Java
> io operation while creating the logs . These log objects are consuming
> extremely memory. It can be seen in the 1 st screenshot that the string
> object for log is getting created and then the log is stored in the backup
> folder .
> :(
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
