Hello,
When processing a FTP-PI-SOAP interface with Content Conversion in the source comm. channel, we are finding the following issue:
- Source files are accessed through Filezilla FTP Server.
- When the source file is correct, the scenario works well and the file, if selected in cc, is successfully moved to an archive folder.
- When the Conversion fails (i.e. more fields than expected) the communication channel successfully detect the Conversion error and:
- If the file size is lower than the parameter "Initial Transfer Buffer Size" in filezilla server (by default 32Kb), the comm. channel works as expected and, if selected in comm. channel config (Archive Faulty Source Files), the file is moved to an /Errors subfolder. It's important to remark that, if the error is found at the end of the file (the last records) it also works well, even when the size is bigger than this parameter.
- If the file size is bigger than the parameter mentioned above, the comm. channel throws a second exception, "Could not process due to error: java.lang.IllegalStateException: Error during RETR epilogue: com.sap.aii.adapter.file.ftp.FTPEx: 426 Unexpected reply codeConnection closed; transfer aborted." and the file is not moved to the /Errors subfolder. Even if we don't select the Archive Faulty Source Files option in sender cc, the FTP error is thrown and the process stops (pending files are not processed).
- We have tried all the config. possibilities in sender communication channel (Passive/Active data connection, Connect Mode = Permanently / Per File Transfer, and so on...).
- We have tried the same scenario in two different PI servers (7.30 and 7.31), and with a different FTP provider as well (Microsoft IIS), but the issue still being the same.
The real scenario should work with files of 2-5 Mb, but the maximum value that Filezilla FTP allows us to put in the Initial Transfer Buffer Size parameter is 1Mb.
I have found some forum entries related to this issue but it only refers to Network/Firewall issues or Disk Space. We are running it in a Filezilla FTP Server deployed on the same host as the PI server, so no firewall present there, and the disk has enough space.
Has anybody with the same issue been able to solve it?