Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Jubula » why my tests connect to AUT timeout sometimes
why my tests connect to AUT timeout sometimes [message #1776283] Wed, 15 November 2017 01:59 Go to next message
mi lei is currently offline mi leiFriend
Messages: 1
Registered: November 2017
Junior Member
i run my tsets use autrun andt testexe but sometime an error occured and i guess it is connection timeout but i do not know how to fix this case and why timeout occur?
the log is :
17-11-15 9:07:03 - AUT is probably started with autrun yet.
17-11-15 9:07:03 - Start working with Test Job: V36FT
17-11-15 9:07:03 - Test Job "V36FT": 7 test suite executions are expected...
17-11-15 9:07:03 - Start working with Test Suite: <createSignalImportProject>
17-11-15 9:07:03 - AUT: Connecting to "V36Test"...
17-11-15 9:07:23 - AUT OK: Connection to AUT could not be established....

09:07:13.930 [Awaiting command: class org.eclipse.jubula.client.internal.commands.ConnectToAutResponseCommand] WARN o.e.j.c.i.c.ConnectToAutResponseCommand - org.eclipse.jubula.client.internal.commands.ConnectToAutResponseCommandtimeout() called
2017-11-15 09:07:23.948 [Worker-0] ERROR o.e.j.c.c.c.AUTConnection - Connection to AUT could not be established.
2017-11-15 09:07:24.161 [Worker-0] ERROR o.e.j.client.internal.BaseConnection - request() called to an unconnected connection
2017-11-15 09:07:24.164 [Worker-0] ERROR o.e.j.c.c.b.TestExecution - AUTConnection fails
org.eclipse.jubula.client.internal.BaseConnection$NotConnectedException: This connection is not connected
at org.eclipse.jubula.client.internal.BaseConnection.request( ~[org.eclipse.jubula.client.api_3.3.0.201705050842.jar:na]
at org.eclipse.jubula.client.core.businessprocess.TestExecution.processCap( [org.eclipse.jubula.client.core_5.0.0.201705050842.jar:na]
at org.eclipse.jubula.client.core.businessprocess.TestExecution.startTestSuite( [org.eclipse.jubula.client.core_5.0.0.201705050842.jar:na]
at org.eclipse.jubula.client.core.businessprocess.TestExecution.executeTestSuite( [org.eclipse.jubula.client.core_5.0.0.201705050842.jar:na]
at org.eclipse.jubula.client.core.ClientTestImpl$ [org.eclipse.jubula.client.core_5.0.0.201705050842.jar:na]
at [org.eclipse.core.jobs_3.8.0.v20160509-0411.jar:na]
2017-11-15 09:07:57.976 [Connection.ReaderThread:Socket[addr=/,port=60000,localport=64086]] WARN o.e.j.c.internal.Communicator - Received response org.eclipse.jubula.client.internal.commands.ConnectToAutResponseCommand@10666a1 *after* timeout expired.
2017-11-15 09:25:03.705 [Connection.ReaderThread:Socket[addr=/,port=64111,localport=64098]] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: Connection to AUT has been lost unexpectedly.
Re: why my tests connect to AUT timeout sometimes [message #1777292 is a reply to message #1776283] Tue, 28 November 2017 08:36 Go to previous message
Marvin Mueller is currently offline Marvin MuellerFriend
Messages: 255
Registered: March 2012
Senior Member

the timeout can happen in multiple cases. Since you are using AUTrun can you verify that the AUT is really started before and that it is not still in the startup?

with regards
Marvin Mueller
Previous Topic:Creating a custom JFace based extension
Next Topic:Jubula not working with Jenkins
Goto Forum:

Current Time: Sat May 21 13:34:27 GMT 2022

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

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

Back to the top