Looks like this issue fell throught the cracks as a Fix version was never assigned.

can you make this a 7.0?

you can try using the --poll option which polls ESP rather than remains connected.  But I'm not sure how that deals with connection errors.  I should test that along with this issue.

Usually I can get 

error message when a component (e.g.: ESP) initiated a SOAP call  on an engine (like Thor) and the called becomes extremely busy or (silently) crashed (so no further communication with caller). By default the SOAP call timeout is 7200 sec (2 hours).

So, when I get this timeout, usually I checked the engines log to get any further information.

(BTW. your platform version is a bit outdated. The latest version is 6.2.24, but I can recommend to use 6.4.8)

Dear All, 

Is there way to solve this issue?

I got this ticket and i asked question here itself rather than opening new ticket.

eclcc: /home/gitlab-runner/builds/bfc714bc/0/.......................................

Info C4539: AutoWorkflow: Try adding ': INDEPENDENT' to + to common up code between workflow items
0 error(s), 64 warning(s)

SOAP rpc error[errorCode = -6 message = timeout expired
Target: C!10.224.84.2, Raised in: /mnt/disk1/jenkins/workspace/LN-Candidate-with-Plugins-6.2.16-1/LN/centos-6.0-x86_64/HPCC-Platform/system/jlib/jsocket.cpp, line 1688
]

The OBT Performance Test uses -fthorConnectTimeout=36000 in 'ecl run...' command for both setup and run test cases.