Bug 479538 - AUTRun - o.e.j.app.autrun.AutRunner - Error occurred while restarting AUT
Summary: AUTRun - o.e.j.app.autrun.AutRunner - Error occurred while restarting AUT
Status: CLOSED WORKSFORME
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: Tools (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 468428
  Show dependency tree
 
Reported: 2015-10-12 03:18 EDT by Markus Tiede CLA
Modified: 2019-07-16 07:54 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Tiede CLA 2015-10-12 03:18:33 EDT 
Our nightly e.g. gdwin81 aut_run.log lists a lot of "Error occurred while restarting AUT" problems:

[...]
2015-10-11 01:35:18.897 [AUT Agent Connection] ERROR o.e.jubula.app.autrun.AutRunner - Error occurred while restarting AUT.
java.net.SocketException: Connection reset
	at java.net.SocketInputStream.read(SocketInputStream.java:196) ~[na:1.7.0_80]
	at java.net.SocketInputStream.read(SocketInputStream.java:122) ~[na:1.7.0_80]
	at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:283) ~[na:1.7.0_80]
	at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:325) ~[na:1.7.0_80]
	at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:177) ~[na:1.7.0_80]
	at java.io.InputStreamReader.read(InputStreamReader.java:184) ~[na:1.7.0_80]
	at java.io.BufferedReader.fill(BufferedReader.java:154) ~[na:1.7.0_80]
	at java.io.BufferedReader.readLine(BufferedReader.java:317) ~[na:1.7.0_80]
	at java.io.BufferedReader.readLine(BufferedReader.java:382) ~[na:1.7.0_80]
	at org.eclipse.jubula.app.autrun.AutRunner$AgentConnectionWatcher.run(AutRunner.java:71) ~[na:na]
[...]
Comment 1 Eclipse Genie CLA 2017-10-03 01:01:55 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.