Eclipse Community Forums: Jubula » why my tests connect to AUT timeout sometimes

Help

Home

Home » Eclipse Projects » Jubula » why my tests connect to AUT timeout sometimes

Show: Today's Messages :: Show Polls :: Message Navigator

why my tests connect to AUT timeout sometimes [message #1776283]

Wed, 15 November 2017 01:59

mi lei

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(BaseConnection.java:157) ~[org.eclipse.jubula.client.api_3.3.0.201705050842.jar:na]
at org.eclipse.jubula.client.core.businessprocess.TestExecution.processCap(TestExecution.java:751) [org.eclipse.jubula.client.core_5.0.0.201705050842.jar:na]
at org.eclipse.jubula.client.core.businessprocess.TestExecution.startTestSuite(TestExecution.java:655) [org.eclipse.jubula.client.core_5.0.0.201705050842.jar:na]
at org.eclipse.jubula.client.core.businessprocess.TestExecution.executeTestSuite(TestExecution.java:372) [org.eclipse.jubula.client.core_5.0.0.201705050842.jar:na]
at org.eclipse.jubula.client.core.ClientTestImpl$1.run(ClientTestImpl.java:580) [org.eclipse.jubula.client.core_5.0.0.201705050842.jar:na]
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) [org.eclipse.core.jobs_3.8.0.v20160509-0411.jar:na]
2017-11-15 09:07:57.976 [Connection.ReaderThread:Socket[addr=/10.93.40.164,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=/10.93.40.164,port=64111,localport=64098]] ERROR o.e.j.c.cmd.AbstractCmdlineClient - An error ocurred: Connection to AUT has been lost unexpectedly.

Report message to a moderator

Re: why my tests connect to AUT timeout sometimes [message #1777292 is a reply to message #1776283]

Tue, 28 November 2017 08:36

Marvin Mueller

Messages: 113
Registered: March 2012

Senior Member

Hello,

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

Report message to a moderator

Previous Topic:	Creating a custom JFace based extension
Next Topic:	Jubula not working with Jenkins

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Sep 20 08:37:00 GMT 2018

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter