Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367327 - Large monitoring reports can cause an OutOfMemory exception
Summary: Large monitoring reports can cause an OutOfMemory exception
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: Core (show other bugs)
Version: 1.2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Juno M5   Edit
Assignee: Markus Tiede CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-21 09:44 EST by Marc Steffens CLA
Modified: 2012-01-03 08:41 EST (History)
1 user (show)

See Also:


Attachments
This patch will prevent the JVM from running OutOfMemory during CRUD operations (17.60 KB, patch)
2011-12-21 09:44 EST, Marc Steffens CLA
markus.tiede: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Steffens CLA 2011-12-21 09:44:27 EST
Created attachment 208680 [details]
This patch will prevent the JVM from running OutOfMemory during CRUD operations

The current database model of Jubula can cause an OutOfMemory exception while connecting to a database containing large monitoring reports or writing a large monitoring report to a database. 

The reason behind this is how monitoring reports will be fetched when the corresponding test result summary will be loaded. This patch will detach the monitoring reports from the test result summaries to prevent an unnecessarily load of the monitoring report, while connecting to a database. 

In addition this patch will add a SessionCustomizer. EclipseLink can be configured to use streams to store large binary data. This can improve the max size for reading/writing on some JDBC drivers.
Comment 2 Oliver Goetz CLA 2012-01-03 08:41:51 EST
Fix verified manually, during several test on different platforms with large monitoring reports the OOM error did not occur