[ 
https://issues.apache.org/jira/browse/CAMEL-13781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

MOHAMMED SOHAIB reopened CAMEL-13781:
-------------------------------------

Team,

 I have compiled our application code with the latest camel-core 2.24.1 with 
JDK 7 and the build generation got failed.

If I use the JDK 8 for camel-core 2.24.1 version of jar files, then the code 
got compiled and build generated successfully.

We are using Java 7 in our applications and our applications are deployed into 
Websphere with JDK 7.

I have attached the code snippets here where we are facing the memory leaks in 
the Java Hash Map.

Please refer the Code Snippet 2 highlighted piece of code. Plz review and 
suggest and if we can use the garbage collector into this hasp map.

I am trying to reproduce this issue with 2.24.1 but when I deploy this jar file 
with the application server WAS, our application is not able to start. Getting 
Library mismatch issue.



Regards,
Md Sohaib.

> Production Memory Leakage Issue
> -------------------------------
>
>                 Key: CAMEL-13781
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13781
>             Project: Camel
>          Issue Type: Bug
>          Components: came-core
>    Affects Versions: 2.17.7
>         Environment: Production
>            Reporter: MOHAMMED SOHAIB
>            Priority: Critical
>         Attachments: Code_Snippet_2.png, Code_snippet_1.png, Pie Chart.png, 
> Problem_Describtion.png, Suspect_Problem.png
>
>
> 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.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to