What happens on java.lang.OutOfMemoryError: PermGen space [message #905384] |
Thu, 30 August 2012 09:30 |
Sascha Mising name Messages: 22 Registered: December 2011 |
Junior Member |
|
|
How is Jubula supposed to react on such errors of the Unit under Test :
!ENTRY com.kuka.common.eclipse 4 0 2012-08-30 10:45:32.217
!MESSAGE Ãœbertragung fehlgeschlagen!
!STACK 0
java.lang.OutOfMemoryError: PermGen space
at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1069)
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128)
at ..
Currently it seems that Jubula is not able to recover / restart the AUT if this happens.
Thu Aug 30 10:45:38 CEST 2012○○Step: click in component
!!Error occurred !!
○5006: Timeout occurred.
Thu Aug 30 10:55:39 CEST 2012○Executing Test Suite "Reaction on alteration of the catalogue content"...
Thu Aug 30 10:55:39 CEST 2012○Preparing execution of Test Suite "Reaction on alteration of the catalogue content"...
!!Error occurred !!
○Could not connect to AUT: EclipseSUTTFS
Thu Aug 30 10:55:39 CEST 2012○AUT:○○Disconnected.
Thu Aug 30 10:55:39 CEST 2012○AUT Agent:○connection closed.
Thu Aug 30 10:55:40 CEST 2012○Exit:○○Code 1
Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.jubula.client.core.ClientTest$1
[Updated on: Thu, 30 August 2012 10:18] Report message to a moderator
|
|
|
Re: What happens on java.lang.OutOfMemoryError: PermGen space [message #907053 is a reply to message #905384] |
Mon, 03 September 2012 08:10 |
|
When the AUT crashes this is recognized by Jubula and the test execution is aborted. Since the state of the AUT, the communications layer and the collected data is completely undefined at this moment Jubula won't try to recover from this kind of error.
If this is a frequent problem with your AUT you might want to try Test Jobs with freshly started AUTs to work around the AUT crashing.
- Achim
|
|
|
Powered by
FUDForum. Page generated in 0.02525 seconds