|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Hi Graziano/anynoe, can you contribute some insight to our findings?
1. We run the Jenkins job after the slave has been activated as a slave-agent launched from browser - result, the job runs to completion with successful termination.
2.We run the slave using the batch command that you attached above - result, the job runs for 7 minutes and then terminates on the server with the "SocketException: connection reset" error below (the actual job on the slave continues to run and completes successfully after about another 3 minutes).
3.If we run the slave as a Service, we receive the connection reset error after about 2-3 minutes.
4.There are no error messages in the Jenkins Server Event Viewer coinciding with the connection reset error under any of the above cases.
5.We did notice a peak on Jenkins CPU usage when the connection was reset.
Error trace
-----------
FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
hudson.remoting.RequestAbortedExcepton: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
at hudson.remoting.RequestAbortedExcepton.wrapForRethrow(RequestAbortedException.java:41)
at hudson.remoting.RequestAbortedExcepton.wrapForRethrow(RequestAbortedException.java:34)
at hudson.remoting.Request.call(Request.java:174)
at hudson.remoting.Request.call(Request.java:722)
and so on