| Summary: | Memory leak in 2.6.2 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Jan Lerby <lerby84> | ||||||||
| Component: | BIRT | Assignee: | Birt-ReportViewer <Birt-ReportViewer-inbox> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | Xiaoying Gu <bluesoldier> | ||||||||
| Severity: | major | ||||||||||
| Priority: | P3 | CC: | bluesoldier, foxm, gebuh, hri123, hustlg, vvuppuluri, yair.lenga | ||||||||
| Version: | unspecified | ||||||||||
| Target Milestone: | 3.7.0 RC2 | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Jan Lerby
Any script dataset exists in the report? Yes there are. I have EventAdapters for report and datasets. They are written in Java. I changed only version of BIRT and memory leak appeared. it had been fixed in 3.7.0RC2 Can you explain what was wrong? We are using 2.6.2 BIRT and we are very close to the release. It is almost impossible to move to 3.7. If there is a patch for the memory leak for 2.6.2 it will help us a lot. Please anybody comment on this. (I actually tested with 3.7 jars and there is no memory leak there) This patch only changes one java class: /org.eclipse.birt.report.engine/src/org/eclipse/birt/report/engine/script/internal/DataSetScriptExecutor.java. Please refer to the last version of this class. You can create a patch for 2.6.2 by yourself, and only change this class. Thanks Gang Liu, it worked for us. What needs to be done to release it as official 2.6.2 patch. Hi, Short Version: - We need "official" fix for this bug (a plugin jar, 2.6.2.1, or 2.6.3). - This is a show stopper for us (and probably for many other large installations). Long Version: My group is working on a an upgrade to large deployment of BIRT (>100 different templates). We have chosen to upgrade to 2.6.2 for two reasons: (a) This version is bundled with the current IBM RAD 8.0.2, and (b) we expected this to be stable version, addressing many of issues of 2.6.0 and 2.6.1. This bug is a show-stopper for us. We found that we get PermGen after ~200 reports. We could not find any workaround for our server-based reporting. We have just invested large number of hours in testing all reports on 2.6.2. Using other version will require complete retest by multiple teams. I would like to ask for an "official" bug fix for the 2.6.2 version. This can be in the form of "plugin" jar that can be installed on top of 2.6.2, or new version (2.6.3, 2.6.2.1, ...). Having an "official" bug fix will allow us to ask for our vendors and other teams to upgrade. With private, source-level patch - there is no real way to coordinate identical deployment across multiple teams, vendors, etc. In general, production teams will not accept this source-level patch. At minimum, we need a way to download a compiled patch (jar, or similar) from "eclipse.com" or "birt-exchange.com". Also, waiting for 3.7 is unrealistic for us (and I suspect for many clients) - the cost associated with upgrade (testing, coordination, waiting for vendor support) is too big. Thanks for looking into this issue. Yair Lenga Created attachment 213155 [details]
1st part
Created attachment 213156 [details]
2nd part
Created attachment 213157 [details]
3rd part
Due to the Bugzilla upload file size limitation, please download all the 3 parts of the patch. Then merge them into org.eclipse.birt.report.engine_2.6.2.r262_v20120326.jar. Use this jar to replace the old org.eclipse.birt.report.engine_xxxx.jar in your plugins folder.
(In reply to comment #11) > Created attachment 213157 [details] > 3rd part > > Due to the Bugzilla upload file size limitation, please download all the 3 > parts of the patch. Then merge them into > org.eclipse.birt.report.engine_2.6.2.r262_v20120326.jar. Use this jar to > replace the old org.eclipse.birt.report.engine_xxxx.jar in your plugins folder. ============================ hi yu chen, i tried to download each of the jars, but i was not able to uncompress or unzip the individual jar files.is there some way you can upload the main jar file. I'm running into the same problem - I can't merge the files into one jar |