You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2019/04/24 10:18:00 UTC
[jira] [Updated] (CXF-7943) MAPCodec: Memory leak due to growing
uncorrelatedExchanges
[ https://issues.apache.org/jira/browse/CXF-7943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated CXF-7943:
-------------------------------------
Fix Version/s: (was: 3.3.2)
> MAPCodec: Memory leak due to growing uncorrelatedExchanges
> ----------------------------------------------------------
>
> Key: CXF-7943
> URL: https://issues.apache.org/jira/browse/CXF-7943
> Project: CXF
> Issue Type: Bug
> Affects Versions: 3.2.0
> Environment: CXF 3.2.0, JDK 1.8
> Reporter: Sean
> Priority: Major
> Attachments: fault_req_resp.xml, histogram.PNG, leak_suspect_1.PNG, mapcodec_leak.png, mem_dump.png, ok_req_resp.xml
>
>
> When running load tests, my system begin to get memory leak after 4 hours or so. When analyzing the heap dump using VisualVM (please see attachments), I can see that a ConcurrentHashMap is taking up 1.7 GB of space in the heap, as well as being the main "suspect" for this leak. This leads me to believe that it is the uncorrelatedExchanges attribute since this map is being reference from the MAPCodec class.
> I believe that the map, in my case, for whatever reason, does not always remove the Exchange after the synchronous request/responses are done, however I could be wrong.
>
> IF this is indeed a bug, what could the cause of this be, as well as any work around?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)