[SLING-5715] Random NoRouteToHostException in Teleporter Client MultipartAdapter method

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JUnit Tests Teleporter 1.0.4
• Fix Version/s: JUnit Tests Teleporter 1.0.8
• Component/s: Testing
• Assignee: Bertrand Delacretaz
• Reporter: Thierry Ygé
• Created: 09/May/16 09:11
• Updated: 14/Sep/16 21:14
• Resolved: 18/May/16 14:12

Description

We observe on jenkins jobs that randomly serverside tests are failing due to "java.net.NoRouteToHostException: Cannot assign requested address"

This is apparently always coming from "org.apache.sling.testing.teleporter.client.MultipartAdapter.<init>(MultipartAdapter.java:42)"

It would be good to check if the implementation is not using "old" or unstable API. maybe replacing it using http component API would help to make it more stable.

06:48:39 [INFO] java.net.NoRouteToHostException: Cannot assign requested address
06:48:39 [INFO] 	at java.net.PlainSocketImpl.socketConnect(Native Method)
06:48:39 [INFO] 	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
06:48:39 [INFO] 	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
06:48:39 [INFO] 	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
06:48:39 [INFO] 	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
06:48:39 [INFO] 	at java.net.Socket.connect(Socket.java:589)
06:48:39 [INFO] 	at java.net.Socket.connect(Socket.java:538)
06:48:39 [INFO] 	at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
06:48:39 [INFO] 	at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
06:48:39 [INFO] 	at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
06:48:39 [INFO] 	at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
06:48:39 [INFO] 	at sun.net.www.http.HttpClient.New(HttpClient.java:308)
06:48:39 [INFO] 	at sun.net.www.http.HttpClient.New(HttpClient.java:326)
06:48:39 [INFO] 	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1168)
06:48:39 [INFO] 	at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1104)
06:48:39 [INFO] 	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)
06:48:39 [INFO] 	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:932)
06:48:39 [INFO] 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1282)
06:48:39 [INFO] 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1257)
06:48:39 [INFO] 	at org.apache.sling.testing.teleporter.client.MultipartAdapter.<init>(MultipartAdapter.java:42)
06:48:39 [INFO] 	at org.apache.sling.testing.teleporter.client.TeleporterHttpClient.uninstallBundle(TeleporterHttpClient.java:92)
06:48:39 [INFO] 	at org.apache.sling.testing.teleporter.client.ClientSideTeleporter$2.evaluate(ClientSideTeleporter.java:174)
...

It is same for uninstall and install bundle operation of Teleporter. Maybe it could be related to SLING-5352, as the test class contains ~115 tests, and maybe that produce issues when Teleporter install/uninstall quickly so many test / bundle.

cc bdelacretaz

Issue Links

• is related to: SLING-5724 Teleporter: Use o.a.s.testing.clients instead of custom HTTP requests in TeleporterHttpClient