Client not connected issue:

Trying to sftp mulitple files with separate sftp instances using the plinq

s.AsParallel().Select(part => productSaver.SaveSnapshot(product, cutoffTime, part))
.ToArray().AsParallel()
.ForAll(file => UploadFile(file, delivery.DeliveryID));

a product has say 16 files to upload, what happens is some files are fully uploaded, while some are partially uploaded, and finally some aren't uploaded at all. I receive the client not connected exception which occurs in the InternalUploadFile. We are leveraging a sftp system called Globalscape, and we have adjusted the server settings to accommodate many sessions, timeouts etc. we have used filezilla and powershell scripts to mimic the process and had success with both. We aren't sure why the ssh session becomes null, and effectively kills the upload.

Start at the InternalUploadFile path named in the report and reproduce the parallel upload using separate SFTP instances, ideally against the described Globalscape setup. Trace when the SSH session becomes null and verify completion by confirming that all files are fully uploaded; the issue names no repository files or tests to run.