Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Jubula » Out of memory while writing test result report(GC overhead limit exceeded - Error while writing Test Result Report)
Out of memory while writing test result report [message #1403067] Mon, 21 July 2014 07:56 Go to next message
Jurjen Hofstra is currently offline Jurjen HofstraFriend
Messages: 34
Registered: March 2013
Member
Hi peoples,

Since a few weeks I'm dealing with an out of memory problem on the Jubula sever:
2014-07-21 05:09:42.412 [Worker-1] ERROR o.e.j.client.core.ClientTestImpl - Error while writing Test Result Report.
java.lang.OutOfMemoryError: GC overhead limit exceeded

I read on this forum about jubula.ini and the xmx option for the textexec command, but I have no idea what values I should use. The xml export file is about 13 MB large and the test takes 6 and a half hours to execute.
The xmx value in the jubula.ini file was 2048; I had increased this to 3072 (-Xmx3072m)
The xmx value for the textexec option is on 5120 since a month or so (-J-Xmx5120M)
The machine has 8 GB ram.

Maybe there are other values that need to be adjusted except these two?

thanks in advance!

kind regards,

Jurjen
Re: Out of memory while writing test result report [message #1403094 is a reply to message #1403067] Mon, 21 July 2014 11:11 Go to previous messageGo to next message
Achim Loerke is currently offline Achim LoerkeFriend
Messages: 363
Registered: July 2009
Location: Braunschweig, Germany
Senior Member

Hi Jurjen,

5GB heap space should be plenty, our nightly regressions run with half that amount.
Which Jubula version are you using, which operating system and which database?
Do you take a lot of screen shots or are a lot taken automatically to documents errors?

- Achim
Re: Out of memory while writing test result report [message #1403102 is a reply to message #1403094] Mon, 21 July 2014 11:36 Go to previous messageGo to next message
Jurjen Hofstra is currently offline Jurjen HofstraFriend
Messages: 34
Registered: March 2013
Member
There are quite a lot of screenshots, 5700 last test run.

I wish I knew how I could stop a particular test when something goes wrong...

Jurjen
Re: Out of memory while writing test result report [message #1403104 is a reply to message #1403102] Mon, 21 July 2014 11:42 Go to previous messageGo to next message
Achim Loerke is currently offline Achim LoerkeFriend
Messages: 363
Registered: July 2009
Location: Braunschweig, Germany
Senior Member

Well, that's what event handlers are for. Check the documentation in the online help.

- Achim
Re: Out of memory while writing test result report [message #1404002 is a reply to message #1403104] Tue, 29 July 2014 06:45 Go to previous message
Jurjen Hofstra is currently offline Jurjen HofstraFriend
Messages: 34
Registered: March 2013
Member
Hi Achim,

Thanks for your answer. I solved the problem. I had event handlers everywhere where things could go wrong. That's why I had 5900 screenshots.
Now I only have event handlers per use case as documented at page 166 of the User Manual. And reentry type Return. If something goes wrong,
the current use case stops and the testing will proceed at the next use case. That's what I want.
Once again thanks!
kind regards,
Jurjen

[Updated on: Tue, 29 July 2014 06:46]

Report message to a moderator

Previous Topic:Create an action for Application
Next Topic:Store multiple values in a Variable
Goto Forum:
  


Current Time: Sun Mar 29 03:16:44 GMT 2015

Powered by FUDForum. Page generated in 0.01783 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software