1219921 - With javaws mm-win7-32 does no longer connect to jenkins master in staging

Status: RESOLVED WORKSFORME

(Mozilla QA Graveyard :: Infrastructure, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

About half an hour ago the connection between the Windows 7 staging node (mm-win7-32) and jenkins master got dropped and since then it does not reconnect to the master. Starting the javaws command opens the Java window but after some seconds it closes again.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

While the javaws command fails to connect, it works fine with the java command. I will further investigate that tomorrow. For now the box should run the remaining jobs in the queue.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Just got the javaws connection error dialog. Here the actual exception:

CouldNotLoadArgumentException[ Could not load file/URL specified: http://mm-ci-staging.qa.scl3.mozilla.com:8080/computer/mm-win-7-32/slave-agent.jnlp]
	at com.sun.javaws.Main.launchApp(Unknown Source)
	at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
	at com.sun.javaws.Main.access$000(Unknown Source)
	at com.sun.javaws.Main$1.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Server returned HTTP response code: 504 for URL: http://mm-ci-staging.qa.scl3.mozilla.com:8080/computer/mm-win-7-32/slave-agent.jnlp
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.access$200(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection$9.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.security.AccessController.doPrivilegedWithCombiner(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
	at com.sun.deploy.net.HttpUtils.followRedirects(Unknown Source)
	at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
	at com.sun.deploy.net.BasicHttpRequest.doRequest(Unknown Source)
	at com.sun.deploy.net.BasicHttpRequest.doGetRequest(Unknown Source)
	at com.sun.javaws.jnl.LaunchDescFactory._buildDescriptor(Unknown Source)
	at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
	at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
	... 5 more

So it's a 504 Gateway error. I feel that this could be related to bug 1170832. Somehow the java command works better. But maybe its already the download of the slave.jar file as done by javaws but not java.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Hm, I tested mm-win7-64 by disconnecting it from staging master and re-connecting via javaws. All works fine on that host.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I tested all settings we usually do on Windows for setup but wasn't able to find a difference. This is mystically. I don't have the time to dig deeper into it right now. As of now I placed an additional Jenkins shortcut on the deskop for the Java command.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+1]]

We have never seen this again.