pub.client.sftp:put not returning expected return code / message
webMethods 10.11 version and SFTP version 2
Hi,
We are using the inbuilt service pub.client.sftp:put service to transfer files to a SFTP target server. On the target server we could see that the files are placed, however the pub.client.sftp:put service returns a failure message. This happens only when we try to send large count of files at a time.
Does anyone know what could be the possible reason why failure is returned even though files are placed successfully.
Below is the error message
Reason for failure - Delivery service for failed with a status of fail and status message of failed to copy the files to Remote - Error while executing command ‘put’: </path/filename> (No such file or directory)
The error message is a bit strange because the file has been placed at the target, but still its throws as no such file while executing put
Perhaps you can ask the Target SFTP Team to verify if similar Failure message is appearing at their Logs too.
Additionally, you can enhance the SFTP(0147 SFTP Client) and Network (0064 Network Services) related Logging Level at your end to Trace or Debug to view if any additional error information gets captured in the Server Logs to aid your investigation.
Note : Enhancing the Logging Level to Trace or Debug will make your Server.log file size to grow exponentially. So ensure to quickly revert to the normal logging Level as soon as possible else your Drive/Disk space where Server.log is written will run out of space and lead to problems.
For Newer Version Administration → Logging configuration → View server logger details Under Integration Server Option
Thank you for the suggestion.
We enhanced the logging levels, but no additional logs related to this error was captured. When we further analyzed the logs, we could see that there was a success response after the file was placed in the target server from ‘put’ service and as per the logic the file was deleted from the local directory. But after few seconds the above failure message was recorded mentioning the ‘put’ service had failed.
One point to note is that, this issue occurs only when large number of files are transferred. In this case around 150+ files was transferred in a single run of the service.
