| Jubula sometimes loses the connection to the AUT [message #1409498] |
Mon, 18 August 2014 05:01  |
Eclipse User |
|
|
|
Hey,
I'm running Jubula 8.0 on an Ubuntu VM to Test a RCP Application with Java 7 32/64bit and Java 8 64bit.
The Tests are started from a Jenkins with a maven script.
Sometimes everything works fine but sometimes the test fails unexpectetly in the middle of a test case with the following error message:
Mon Aug 18 06:55:27 CEST 2014 Test Case: Select Context Menu entry
Mon Aug 18 06:55:27 CEST 2014 Step: select ContextMenu entry by textpath
!!Error occurred !!
Connection to AUT has been lost unexpectedly.
Mon Aug 18 06:55:33 CEST 2014 Writing Report to Database
Mon Aug 18 06:55:36 CEST 2014 Writing Report into file-system
Mon Aug 18 06:55:39 CEST 2014 AUT: Disconnected.
Mon Aug 18 06:55:39 CEST 2014 AUT Agent: connection closed.
Mon Aug 18 06:55:39 CEST 2014 Exit: Code 1
The AUT Agent is still running when it fails.
In the Client.log you see the following message:
2014-08-18 06:55:33.105 [Connection.ReaderThread:Socket[addr=/127.0.0.1,port=43272,localport=49256]] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: Connection to AUT has been lost unexpectedly.
2014-08-18 06:55:33.217 [Connection.ReaderThread:Socket[addr=localhost/127.0.0.1,port=60000,localport=45233]] ERROR o.e.j.c.c.c.StartAUTServerStateCommand - AUTServer could not start: unknown AUTServer exit code: '137'
Here is the config file for the test execution:
<configuration>
<project>ScoutIntegrationTests</project>
<version>1.0</version>
<dburl>jdbc:h2:~/.jubula/database/embedded;MVCC=TRUE;AUTO_SERVER=TRUE;DB_CLOSE_ON_EXIT=FALSE</dburl>
<dbscheme>Default Embedded (H2)</dbscheme>
<dbuser>sa</dbuser>
<dbpw></dbpw>
<autconfig>EclipseKeplerAUT@localhost_linux</autconfig>
<server>localhost</server>
<port>60000</port>
<language>de_DE</language>
<testsuite>PRODUCTIVE</testsuite>
<datadir>.</datadir>
<resultdir>./target</resultdir>
</configuration>
Thanks and Regards,
Sandro
[Updated on: Tue, 19 August 2014 01:44] by Moderator |
|
|
|
| Re: Jubula sometimes loses the connection to the AUT [message #1409855 is a reply to message #1409607] |
Tue, 19 August 2014 02:22  |
| Eclipse User |
|
|
|
Hi Alex,
In the rc log is just multiple times the following warning:
2014-08-18 06:46:28.638 [Connection.ReaderThread:Socket[addr=BSIVD5248/127.0.1.1,port=45337,localport=37356]] WARN o.e.j.r.c.c.AbstractCapTestCommand - unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@4aba2808[component type=org.eclipse.swt.widgets.Table,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Table_1]]'.
org.eclipse.jubula.rc.common.exception.ComponentNotFoundException: unmanaged component with identifier: 'org.eclipse.jubula.tools.objects.ComponentIdentifier@4aba2808[component type=org.eclipse.swt.widgets.Table,alternative name=<null>,hierarchy=[org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Shell_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Composite_1, org.eclipse.swt.widgets.Table_1]]'.
at org.eclipse.jubula.rc.swt.listener.ComponentHandler.findComponent(ComponentHandler.java:178) ~[org.eclipse.jubula.rc.swt.jar:na]
at org.eclipse.jubula.rc.swt.commands.CAPTestCommand.findComponent(CAPTestCommand.java:43) ~[org.eclipse.jubula.rc.swt.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.getImplClass(AbstractCapTestCommand.java:133) [org.eclipse.jubula.rc.common.jar:na]
at org.eclipse.jubula.rc.common.commands.AbstractCapTestCommand.execute(AbstractCapTestCommand.java:234) [org.eclipse.jubula.rc.common.jar:na]
at org.eclipse.jubula.communication.Communicator$ConnectionListener.received(Communicator.java:815) [org.eclipse.jubula.communication.jar:na]
at org.eclipse.jubula.communication.connection.Connection.fireMessageReceived(Connection.java:401) [org.eclipse.jubula.communication.jar:na]
at org.eclipse.jubula.communication.connection.Connection.access$2(Connection.java:390) [org.eclipse.jubula.communication.jar:na]
at org.eclipse.jubula.communication.connection.Connection$ReaderThread.run(Connection.java:453) [org.eclipse.jubula.communication.jar:na]
This was 10 minutes before the test fails so I don't think that there is any connection to the actual problem.
As far as I know, the error can occur with all java versions.
The same test are also running on a windows 7 and windows 8 machine without problems so there shouldn't be an error in the test itself.
To the linux machine, it's a ubuntu 13.10 with gnome 3.8.4.
Best regards,
Sandro
|
|
|
Powered by
FUDForum. Page generated in 0.05890 seconds
Home