Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Invalid
-
2.17.7
-
None
-
None
-
Production
-
Unknown
Description
Dear Team,
There is frequent memory leakage problem on production WAS server and We have analyzed the heap dump, thread dumps and garbage collection logs and below are the Observations from our analysis.
We observed the memory leakage problem with the below package,
org/apache/camel/com/googlecode/concurrentlinkedhashmap/ConcurrentLinkedHashMap
The memory leakage might be happening in the camel jar file "camel-core-2.17.7.jar" as per the leakage suspect analysis which is used in our custom application name "RestWebServices"
Below are the observations from the logs analysis.
Leak suspect 1.
1,403,578,672 bytes (53.36 %) of Java heap is used by 254 instances of java/util/HashMap$Entry
Contains an instance) of the leak suspect:
- org/apache/camel/com/googlecode/concurrentlinkedhashmap/ConcurrentLinkedHashMap$Node holding 228,815,984 bytes at 0x71fb89c88
Leak Suspect 2.
977,860,416 bytes (37.17 %) of Java heap is used by 9,682 instances of org/apache/http/impl/conn/PoolingHttpClientConnectionManager
Leak suspect 3.
A Linked List Data Structure Detected.
228,816,192 bytes (8.7 %) of Java heap is used by 759 instances of org/apache/camel/com/googlecode/concurrentlinkedhashmap/ConcurrentLinkedHashMap$Node
Contains 2 types of the following objects:
- 759 instances of java/lang/String holding 139,656 bytes
- 759 instances of org/apache/camel/com/googlecode/concurrentlinkedhashmap/ConcurrentLinkedHashMap$WeightedValue holding 228,658,112 bytes
-Contained under array of java/util/HashMap$Entry holding 1,403,578,672 bytes at 0x70e6cd110
========================================================
Kindly review this problem and suggest possible solutions as soon as possible.
Regards,
Md Sohaib.
