Community
Participate
Working Groups
Build Identifier: BIRT 3.7.2 RC1 Hello, My Birt reports are deployed using the WebViewerExample (Birt runtime 3.7.2_RC1) on Tomcat 7.0.23 on Linux (RHEL) server. Every time a report is accessed, the PermGen spikes by 2-6 MB (varies for different reports). This increase is in just showing the Parameter input box to the user. On generating the report, there is a further increase of 2-5 MB in the PermGen usage. Please note that on previous 2.6.x version of BIRT runtime, the increase was almost twice as much, so the 3.7.x version is indeed better but still takes Tomcat towards sure crash due to OutOfMemory. Please advise how this can be reduced/rectified. If it's related to some third party code (eg: Rhino js.jar), then can there be any workarounds built around the issue. Even if a work-around makes the report a bit slower, it is still better than guaranteed crashing. Thanks -Sebastian Reproducible: Always Steps to Reproduce: 1. Create any report which requires one or more parameters to be entered by the user. 2. Deploy this on Tomcat (mine is 7.0.23) using BIRT WebViewerExample webapp 3. Monitor the Tomcat's PermGen just before and after accessing the report(I do it using a custom jsp page which uses MemoryPoolMXBean).
