tracker issue : CF-4199795

select a category, or use search below
(searches all categories and all time range)

An error occurred during the sFTP getfile operation. correct/incorrect error

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/PRNeedInfo

Reporter/Name(from Bugbase): Chris Hopkins / Chris Hopkins ()

Created: 09/21/2017

Components: Language, Exception Handling

Versions: 11.0

Failure Type: Data Loss

Found In Build/Fixed In Build: 11 /

Priority/Frequency: Normal / Some users will encounter

Locale/System: English / Win 2008 Server R2 64 bit

Vote Count: 0

Problem Description:

Hi, unsure if this is a bug or what but its a little confusing.

When performing many SFTP getFile operations and the script times out due to the admin timeout setting the error returned is as shown below, which is correct but it is masking the fact that this happened due to the timeout which makes it a bit of a pain to debug. 

It would be awesome if the real issue could also be shown - whatever that may be in any case.

Steps to Reproduce:

loop lots of SFTP getfile operations until the time goes over the cfadmin timeout setting

Actual Result:


Action: getfile
Detail: Error: ''.  Check for a bad path, filename, or directory.
Message: An error occurred during the sFTP getfile operation.
StackTrace:$SftpOperationBadPathException: An error occurred during the sFTP getfile operation.

Expected Result:

Something to let me know what the actual error was ( that the timeout had stopped the operation )

Any Workarounds:




Sorry please ignore might have jumped the gun on this one, this definitely seemed to be the case at the time but its now happening with a 50,000 second timeout after a few minutes so it must have just been coincidental that we stopped hitting something else at the same time as changing that setting.
Comment by Chris H.
309 | September 21, 2017 01:43:40 PM GMT
Hi Chris, Please share a code snippet where you are hitting the issue, so that we will be able to narrow it down and debug the issue. Thanks!
Comment by S P.
310 | October 09, 2017 05:44:39 AM GMT
Hi Chris, Also, please do share the complete stack trace & the log files. Thanks!
Comment by S P.
311 | October 12, 2017 07:43:11 AM GMT
Since there has been no response on this issue, closing the bug for now. But if you still do see the issue do let us know, we would re-open the ticket. Thanks!
Comment by S P.
312 | November 06, 2017 04:54:47 AM GMT