Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 396016

Summary:	Improve export so that larger projects can be exported without running into memory problems
Product:	[Technology] Jubula	Reporter:	Alexandra Schladebeck <alexandra.schladebeck>
Component:	Core	Assignee:	Project Inbox <jubula.core-inbox>
Status:	CLOSED FIXED	QA Contact:	Oliver Goetz <Oliver.Goetz>
Severity:	enhancement
Priority:	P2	CC:	Achim.Loerke, philipp
Version:	1.3.0	Keywords:	triaged
Target Milestone:	2.3
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Alexandra Schladebeck

2012-12-07 01:56:31 EST

Exporting larger projects can result in out of memory problems at the moment due to the fact that the export is produced as one long string. 

These problems can often be avoided or worked around to some degree by working on a 64-bit machine and / or increasing the memory allocated to the ITE. 

However, at a certain size, the export is still too large for these measures. 

We have discussed that this problem can be resolved by writing the exported XML file in smaller chunks.

Comment 1 Alexandra Schladebeck

2012-12-07 01:57:42 EST

As discussed:

The first step would be to split up the export so that the Test Cases and the Test Result Summaries are exported separately, as the Test Result Summaries often constitute a large part of the export. The summaries could themselves also be split up so that they are exported in small groups. 

The second step would be to also incrementally export the Test Specification as well. 

If only the first step is done at first, then please reopen this issue to track progress on the second step.

Comment 2 Alexandra Schladebeck

2013-11-15 04:44:00 EST

This is something that we want to look at for the next release.

Comment 3 Alexandra Schladebeck

2013-11-22 02:53:14 EST

We've done some major improvement on the export with:

http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=06df02a29045fc7cecd348246144c6a8a922b959

Marking this ticket as fixed.

Comment 4 Oliver Goetz

2013-12-05 05:53:47 EST

I was able to export and import our biggest project ite from the testweek DB using the 32- and 64-bit versions of Jubula/GUIdancer without any modifications to increase the allocated memory via the ITE. The project was exported and imported correctly and the test result summaries were available (I checked for the last 365 days).
Using the DBTool I was only able to export the project when using the 64bit-version. When trying to perform an export using the 32bit version I got the error message 

"The JVM found at K:\guidancer\Workspace\hu_snapshot\current\platforms\win32.win3
2.x86\jre is damaged.
Please reinstall or define EXE4J_JAVA_HOME
to point to an installed 32-bit JDK or JRE.
The JVM could not be started. The maximum heap size (-Xmx) might be too large or
 an antivirus or firewall tool could block the execution."

This also occurred when trying to export a smaller project like caa_javafx. 

Using the 64bit-version worked fine as expected.

Comment 5 Alexandra Schladebeck

2014-03-24 10:49:26 EDT

Closing this and adding a new bug for the problem Oli described.

Comment 6 Alexandra Schladebeck

2014-03-24 10:51:06 EDT

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=431028

Comment 7 Oliver Goetz

2014-03-25 09:34:35 EDT

Closed due to comment 6