Bug 516315 - out o fmemory error leading to native memory issue
Summary: out o fmemory error leading to native memory issue
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BIRT (show other bugs)
Version: 4.2.2   Edit
Hardware: Power PC Unix All
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Birt-ReportEngine-inbox@eclipse.org CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-08 10:06 EDT by Jackie Paradis CLA
Modified: 2017-05-08 10:06 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jackie Paradis CLA 2017-05-08 10:06:40 EDT 
Using BIRT 4.2.2 on Power Series/WAS with AIX 7.1
Min and Max Java heap set at 2.6GB
We have 12GB RAM configure for the vm.
Development is using the sample web application as provided in the package.

Originally we had out of memory Java heap error with a min/max Java heap set to 2.5GB, we upped this to 2.6 GB and now we are seeing the server memory growing and reaching max paging space.  We have to recycle the WAS server(JVM) to regain the memory on the server.

This is easily reproducible by running various reports one after the other until memory usage on the server reaches 100% and paging starts.
Also closing the viewer window before the report has loaded will cause the issue as well.
  
We have isolated the following classloader as the culprit:
org/mozilla/javascript/DefiningClassLoader

It can reach up to 20K classes loaded when reviewing the javacore.  We have played with the following jvm parameter 

 -Xgc:classUnloadingKickoffThreshold

and although we have had some success, eventually, we still run out of native memory.  

Any and all help with this issue is appreciated