Bugzilla – Full Text Bug Listing
| Summary: | Large monitoring reports can cause an OutOfMemory exception | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Marc Steffens <Marc.Steffens> | ||||
| Component: | Core | Assignee: | Markus Tiede <markus.tiede> | ||||
| Status: | CLOSED FIXED | QA Contact: | Oliver Goetz <Oliver.Goetz> | ||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | markus.tiede | ||||
| Version: | 1.2.0 | ||||||
| Target Milestone: | Juno M5 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Patch applied with changeset http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=4b1758b48da7126dfa1fa450e10889c3f95d45f3 Fix verified manually, during several test on different platforms with large monitoring reports the OOM error did not occur |
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.