com.uc4.ftpjob.DataTransferException: inputstream is closed.
RA FTP jobs transferring a high number of files fail with one of the following error messages in the report:
Caused by: com.uc4.ftpjob.DataTransferException: Pipe closed. at com.uc4.ftpjob.commands.impl.CopyCommand.throwDataException(CopyCommand.java:707) at com.uc4.ftpjob.commands.impl.CopyCommand.execute(CopyCommand.java:642) at com.uc4.ftpjob.commands.ThreadPoolJobExecutor$ThreadRunner.run(ThreadPoolJobExecutor.java:86) ... 5 more Caused by: java.io.IOException: Pipe closed at java.io.PipedInputStream.read(Unknown Source) at java.io.PipedInputStream.read(Unknown Source) at com.jcraft.jsch.ChannelSftp.fill(ChannelSftp.java:2615) at com.jcraft.jsch.ChannelSftp.header(ChannelSftp.java:2641) at com.jcraft.jsch.ChannelSftp.access$500(ChannelSftp.java:38) at com.jcraft.jsch.ChannelSftp$2.read(ChannelSftp.java:1284) at com.jcraft.jsch.ChannelSftp$2.read(ChannelSftp.java:1234) at com.uc4.ftpjob.commands.impl.CopyCommand.execute(CopyCommand.java:624)
or
Caused by: com.uc4.ftpjob.DataTransferException: inputstream is closed. at com.uc4.ftpjob.commands.impl.CopyCommand.throwDataException(CopyCommand.java:707) at com.uc4.ftpjob.commands.impl.CopyCommand.execute(CopyCommand.java:642) at com.uc4.ftpjob.commands.ThreadPoolJobExecutor$ThreadRunner.run(ThreadPoolJobExecutor.java:86) ... 5 more Caused by: java.io.IOException: inputstream is closed at com.jcraft.jsch.ChannelSftp.fill(ChannelSftp.java:2617) at com.jcraft.jsch.ChannelSftp.header(ChannelSftp.java:2641) at com.jcraft.jsch.ChannelSftp.access$500(ChannelSftp.java:38) at com.jcraft.jsch.ChannelSftp$2.read(ChannelSftp.java:1284) at com.jcraft.jsch.ChannelSftp$2.read(ChannelSftp.java:1234) at com.uc4.ftpjob.commands.impl.CopyCommand.execute(CopyCommand.java:624)
Environment
OS Version: N/A
Cause
Cause type: Other Root Cause: The error message indicates that the network connection was closed during the file transfer. One reason could be a network problem. For example, a short network outage can cause an ftp transfer to terminate as there is no automated error recovery. Problems like this are not a result of defects within the Automic software.
Resolution
N/A
Fix Status: No Fix
Fix Version(s): N/A
Additional Information
Workaround : A potential workaround would be to create a process loop to retry the transfer for a certain number of retries, as it might work on the 2nd try if the connection is available.
Also an Automic File Transfer would be a better solution as this type of File Transfer does error recovery until the file is transferred successfully.