-
Bug
-
Resolution: Not A Defect
-
Critical
-
Jenkins ver. 1.480.3 on SUSE 11
I'm having a slave node to run the FitNesse test cases using the FitNesse plugin.
However when the executing time of test suite is long (over 20 minutes), Jenkins will raise the Java read timed out Exception during the executing time, and the jenkins job is failed.
The error is as follow:
Connected: 200/OK
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
at sun.net.www.http.ChunkedInputStream.readAheadBlocking(ChunkedInputStream.java:543)
at sun.net.www.http.ChunkedInputStream.readAhead(ChunkedInputStream.java:600)
at sun.net.www.http.ChunkedInputStream.read(ChunkedInputStream.java:687)
at java.io.FilterInputStream.read(FilterInputStream.java:133)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:2959)
at sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.read(HttpURLConnection.java:2953)
at hudson.plugins.fitnesse.FitnesseExecutor.getHttpBytes(FitnesseExecutor.java:249)
at hudson.plugins.fitnesse.FitnesseExecutor$1.run(FitnesseExecutor.java:226)
at java.lang.Thread.run(Thread.java:722)
Force close of input stream.
This seems to be a known issue in the FitNesse plugin, and it has been raised for a long time. Hope this bug could be resolved ASAP.
Issue raised before:
https://issues.jenkins-ci.org/browse/JENKINS-18501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel