Our matrix jobs succeeds but the main job fails. It appears that the matrix build will upload the artifact sucessfully and log will show success. But after that point the main job will sit there for about 30 minutes before it exits with:

09:23:23 [CmTriggerMatrixBuild] MD5 of Spider-linux-centos_bullseye.tgz is correct.
09:23:23 [CmTriggerMatrixBuild] Transfer of Spider-linux-centos_bullseye.tgz completed successfully.

---> above is after successfull upload from matrix then below sits for about 30 minutes:

10:21:40 [CmJavaTrigger] Java Result: 1
10:21:40 [CmTriggerMatrixBuild] #GroovyParam# MatrixUrl = http://hcde.hlit.local:8081/job/Spider-test_dev_c-matrix/0
10:21:40 [CmTriggerMatrixBuild] #GroovyParam# MatrixJob = Spider-test_dev_c-matrix
10:21:40 [CmTriggerMatrixBuild] #GroovyParam# MatrixBuildNum = 0
10:21:40 [CmTriggerMatrixBuild] #GroovyParam# MatrixSuccess = false
10:21:40 [CmTriggerMatrixBuild] Matrix job Spider-test_dev_c-matrix finished with error (buildnum=0).
10:21:40
10:21:40 BUILD FAILED
10:21:40 z:\jm\workspace\Spider-test_dev_c\build.xml:865: Jenkins-cli return error:1 Message:Started Spider-test_dev_c-matrix #23
10:21:40 Feb 06, 2016 10:21:39 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run
10:21:40 SEVERE: I/O error in channel CLI connection to http://hcde.hlit.local:8081
10:21:40 java.net.SocketException: Connection reset

The jenkins master log shows:
SEVERE: I/O error in channel CLI channel from /10.20.101.97

We cannot identify any network issues?

Env: The Spider-test_Dev_c and Spider-test_Dev_c-matrix "Builder Label" are windows vm's
and the Matrix jobs builds on windows and Centos (docker).

This has been working in the past for quite a while with no issues?