[
https://issues.apache.org/jira/browse/SLING-5715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277747#comment-15277747
]
Bertrand Delacretaz commented on SLING-5715:
--------------------------------------------
I suspect it might be a connection or other network related resource that's not
released properly, in which case running lots of tests quickly should make this
more likely. Does that match your observations? Or do you have other hints on
how to reproduce this issue?
> Random NoRouteToHostException in Teleporter Client MultipartAdapter method
> --------------------------------------------------------------------------
>
> Key: SLING-5715
> URL: https://issues.apache.org/jira/browse/SLING-5715
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: JUnit Tests Teleporter 1.0.4
> Reporter: Thierry Ygé
>
> 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.
> {noformat}
> 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)
> ...
> {noformat}
> 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]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
