Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » RCP Testing Tool » Failed to close report node: Connection reset(I've often encountered this bug)
Failed to close report node: Connection reset [message #1773708] Tue, 03 October 2017 09:00 Go to next message
Minh Tu Ton That is currently offline Minh Tu Ton ThatFriend
Messages: 17
Registered: January 2015
Junior Member
Hello all,

I'm running RCPTT via the runner. Sometimes the AUT is restarted and the test following the restart is marked as failed with the message "Connection reset". Do you have any idea how this could happen ?

The following is what I have in the log:

!ENTRY org.eclipse.rcptt.launching 4 0 2017-10-02 12:11:46.878
!MESSAGE error getting interpreter state
!SUBENTRY 1 org.eclipse.rcptt.ecl.core 4 0 2017-10-02 12:11:46.878
!MESSAGE Failed to write org.eclipse.rcptt.ecl.core.impl.SaveStateImpl@77a4e30 (host: null)
!STACK 0
java.net.SocketException: Broken pipe (Write failed)
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:134)
	at java.io.DataOutputStream.writeByte(DataOutputStream.java:153)
	at org.eclipse.rcptt.ecl.internal.core.EMFStreamPipe.write(EMFStreamPipe.java:145)
	at org.eclipse.rcptt.ecl.client.tcp.EclTcpSession$1.run(EclTcpSession.java:93)
	at java.lang.Thread.run(Thread.java:748)

!ENTRY org.eclipse.rcptt.launching 4 0 2017-10-02 12:11:46.880
!MESSAGE Couldn't open ECL session
!STACK 0
java.net.ConnectException: Connection refused (Connection refused)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at java.net.Socket.connect(Socket.java:538)
	at org.eclipse.rcptt.ecl.client.tcp.EclTcpSession.initSocket(EclTcpSession.java:142)
	at org.eclipse.rcptt.ecl.client.tcp.EclTcpSession.<init>(EclTcpSession.java:74)
	at org.eclipse.rcptt.ecl.client.tcp.EclTcpClientManager.startClientSession(EclTcpClientManager.java:26)
	at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.createEclSession(BaseAutLaunch.java:984)
	at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.execute(BaseAutLaunch.java:200)
	at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.execute(BaseAutLaunch.java:167)
	at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.execute(BaseAutLaunch.java:161)
	at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.shutdownPlayer(BaseAutLaunch.java:778)
	at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.doExecute(BaseAutLaunch.java:737)
	at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.execTestOrEclContext(BaseAutLaunch.java:634)
	at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.execElement(BaseAutLaunch.java:547)
	at org.eclipse.rcptt.internal.launching.aut.BaseAutLaunch.run(BaseAutLaunch.java:521)
	at org.eclipse.rcptt.internal.launching.ecl.EclScenarioExecutable.doExecuteTest(EclScenarioExecutable.java:91)
	at org.eclipse.rcptt.internal.launching.ecl.EclScenarioExecutable.doExecute(EclScenarioExecutable.java:71)
	at org.eclipse.rcptt.internal.launching.DataExecutable.execute(DataExecutable.java:89)
	at org.eclipse.rcptt.internal.launching.Executable.executeAndRememberResult(Executable.java:127)
	at org.eclipse.rcptt.internal.launching.Executable.executeAndRememberResult(Executable.java:138)
	at org.eclipse.rcptt.internal.launching.Q7LaunchManager$SessionRunnable.run(Q7LaunchManager.java:143)
	at org.eclipse.rcptt.internal.launching.Q7LaunchManager$ExecThread$1.run(Q7LaunchManager.java:716)
	at java.lang.Thread.run(Thread.java:748)

!ENTRY org.eclipse.rcptt.runner 4 0 2017-10-02 12:11:47.151
!MESSAGE 
Retry 1 of 3


!ENTRY org.eclipse.rcptt.runner 1 0 2017-10-02 12:11:47.153
!MESSAGE AUT-0:Restarting  (restartId=1)

!ENTRY org.eclipse.rcptt.launching.ext 1 0 2017-10-02 12:11:49.220
!MESSAGE RCPTT: Launching AUT: AUT_1: Detected AUT architecture is x86_64.64bit arch is selected because AUT uses launcher library
	"plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.401.v20161122-1740" specified in config file: eclipse.ini

!ENTRY org.eclipse.rcptt.launching.ext 1 0 2017-10-02 12:11:49.224
!MESSAGE RCPTT: Launching AUT: AUT_1: Selected JVM is /opt/public/common/jdk1.8.0_131.x64 detected architecture is x86_64

!ENTRY org.eclipse.rcptt.launching.ext 1 0 2017-10-02 12:11:49.224
!MESSAGE RCPTT: Launching AUT: AUT_1: JVM and AUT architectures are compatible: true. JVM is 64bit and support running 32bit: false

...

!ENTRY org.eclipse.rcptt.launching 1 0 2017-10-02 12:12:17.557
!MESSAGE Activating AUT at host localhost. ECL port: 7001. Tesla port: 7002

!ENTRY org.eclipse.rcptt.runner 1 0 2017-10-02 12:12:17.759
!MESSAGE [AUT-0] Finished: CheckAndUpdatePattern.test in 33766, Failed to close report node (2 from 32)


Best regards,

Report message to a moderator

Re: Failed to close report node: Connection reset [message #1774254 is a reply to message #1773708] Thu, 12 October 2017 09:13 Go to previous messageGo to next message
Viktoria Dlugopolskaya is currently offline Viktoria DlugopolskayaFriend
Messages: 124
Registered: March 2017
Senior Member
Hi Tu Ton,

Could you attach a log file of the AUT? The error you mentioned is caused by a disconnection between the AUT and runner, so the main reason may be written to its log.
Also please check this article, it may help: https://wiki.eclipse.org/RCPTT/Common_problems_on_Linux

Report message to a moderator

Re: Failed to close report node: Connection reset [message #1774676 is a reply to message #1774254] Wed, 18 October 2017 14:02 Go to previous messageGo to next message
Minh Tu Ton That is currently offline Minh Tu Ton ThatFriend
Messages: 17
Registered: January 2015
Junior Member
Hello,

I've attached the log from the aut:
- hs_err_pid1173.log is the direct error log from the aut
- aut-ws-0.log is the log from the main aut workspace
- aut-ws-0_restarted_1.log is the log from the aut workspace when the restart happened.

It seems to relate to a bug mentioned in your article but I tried to put -Dorg.eclipse.swt.browser.DefaultType=mozilla in vmargs (see in the log) and the connection reset still happens.

Do you have any clue about this?

Best regards,

[Updated on: Wed, 18 October 2017 14:08]

Report message to a moderator

Re: Failed to close report node: Connection reset [message #1775423 is a reply to message #1774676] Mon, 30 October 2017 08:03 Go to previous message
Viktoria Dlugopolskaya is currently offline Viktoria DlugopolskayaFriend
Messages: 124
Registered: March 2017
Senior Member
Based on errors in 'hs_err_pid1173.log' file, it may be a GTK issue (need to update platform version to 4.5 or update GTK to 3.10.x)
Details here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=427776

Also, you can try to use a workaround to force AUT to use GTK 2: add to application args (before '-vmargs') in AUT's eclipse.ini the following arg:
--launcher.GTK_version
2
After that, re-add the AUT

Report message to a moderator

Previous Topic:How to differentiate between menu entries with the same name
Next Topic:RCPTT with Selenium
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Apr 25 20:28:02 GMT 2024

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

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

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly