Our Products:   CompleteFTP  edtFTPnet/Free  edtFTPnet/PRO  edtFTPj/Free  edtFTPj/PRO
0 votes
14 views
asked in FAQ: edtFTPnet/PRO by (150 points)
edited by

Using SFTP, different target systems react differently, one system (Tibco MFT) creates an extra folder with the same name as the xml-file, is this caused by Edtftpj-pro?

Snapshot logging communication with system (Tibco MFT) that creates extra folder:

2018-11-11 13:18:17 DEBUG SftpClient: put(/Users/j.wierda/home/vpftptest/data/ftpqueue_in/P5L.MGL.KLACHTAFHANDELING/20181109_MGL_AFH_005707.XML,20181109_MGL_AFH_005707.XML)
2018-11-11 13:18:17 DEBUG SftpSubsystemClient: getAttributes('/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML')
2018-11-11 13:18:17 DEBUG SubsystemChannel: Sending SSH_FXP_STAT (path=/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML,id=3)
2018-11-11 13:18:17 DEBUG ConnectionProtocol: Sending 4 bytes for channel id 0 (maxSize=32648)
2018-11-11 13:18:17 DEBUG ChannelDataWindow: remote window consumed 4 bytes of window space (4095974 bytes left)
2018-11-11 13:18:17 DEBUG TransportProtocolCommon: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
2018-11-11 13:18:17 DEBUG TransportProtocolOutputStream: Sent message. Seq no=13, msg=94
2018-11-11 13:18:17 DEBUG ConnectionProtocol: Sent 4 bytes (4 total) for channel id 0
2018-11-11 13:18:17 DEBUG ConnectionProtocol: Sent total bytes 4 for channel id 0
2018-11-11 13:18:17 DEBUG ConnectionProtocol: Sending 50 bytes for channel id 0 (maxSize=32648)
2018-11-11 13:18:17 DEBUG ChannelDataWindow: remote window consumed 50 bytes of window space (4095924 bytes left)
2018-11-11 13:18:17 DEBUG TransportProtocolCommon: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
2018-11-11 13:18:17 DEBUG TransportProtocolOutputStream: Sent message. Seq no=14, msg=94
2018-11-11 13:18:17 DEBUG ConnectionProtocol: Sent 50 bytes (50 total) for channel id 0
2018-11-11 13:18:17 DEBUG ConnectionProtocol: Sent total bytes 50 for channel id 0
2018-11-11 13:18:17 DEBUG TransportProtocolCommon: Received unregistered message: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
2018-11-11 13:18:17 DEBUG AsyncService: Routing SSH_MSG_CHANNEL_DATA
2018-11-11 13:18:17 DEBUG ConnectionProtocol: Received 33 bytes of data for channel id 0
2018-11-11 13:18:17 DEBUG ChannelDataWindow: local window consumed 33 bytes of window space (130929 bytes left)
2018-11-11 13:18:17 DEBUG SubsystemMessageStore: Received SSH_FXP_ATTRS subsystem message
2018-11-11 13:18:17 DEBUG AsyncService: Finished processing SSH_MSG_CHANNEL_DATA
2018-11-11 13:18:17 DEBUG SshMessageStore: Waiting for max 30000 ms
2018-11-11 13:18:17 DEBUG SftpClient: put(remote path=/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML/20181109_MGL_AFH_005707.XML, append=false,resume=false)
2018-11-11 13:18:17 DEBUG SftpSubsystemClient: getAttributes('/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML/20181109_MGL_AFH_005707.XML')
2018-11-11 13:18:17 DEBUG SubsystemChannel: Sending SSH_FXP_STAT (path=/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML/20181109_MGL_AFH_005707.XML,id=4)


Other target systems react as expected and only transfer the file without creating the extra directory, snapshot below from one of them:

2018-11-11 13:36:45 DEBUG AsyncService: Finished processing SSH_MSG_CHANNEL_DATA
2018-11-11 13:36:45 DEBUG SftpClient: cd(actual=/TMGDKLACHTEN)
2018-11-11 13:36:45 DEBUG SshMessageStore: Waiting for max 30000 ms
2018-11-11 13:36:45 DEBUG SubsystemChannel: Sending SSH_FXP_CLOSE (id=6)
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sending 4 bytes for channel id 0 (maxSize=32648)
2018-11-11 13:36:45 DEBUG ChannelDataWindow: remote window consumed 4 bytes of window space (4294967191 bytes left)
2018-11-11 13:36:45 DEBUG TransportProtocolCommon: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
2018-11-11 13:36:45 DEBUG TransportProtocolOutputStream: Sent message. Seq no=17, msg=94
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sent 4 bytes (4 total) for channel id 0
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sent total bytes 4 for channel id 0
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sending 15 bytes for channel id 0 (maxSize=32648)
2018-11-11 13:36:45 DEBUG ChannelDataWindow: remote window consumed 15 bytes of window space (4294967176 bytes left)
2018-11-11 13:36:45 DEBUG TransportProtocolCommon: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
2018-11-11 13:36:45 DEBUG TransportProtocolOutputStream: Sent message. Seq no=18, msg=94
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sent 15 bytes (15 total) for channel id 0
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sent total bytes 15 for channel id 0
2018-11-11 13:36:45 DEBUG SftpSubsystemClient: Waiting for response
2018-11-11 13:36:45 DEBUG TransportProtocolCommon: Received registered message: Name=SSH_MSG_IGNORE,MessageId=2
2018-11-11 13:36:45 DEBUG TransportProtocolCommon: Received unregistered message: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
2018-11-11 13:36:45 DEBUG AsyncService: Routing SSH_MSG_CHANNEL_DATA
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Received 28 bytes of data for channel id 0
2018-11-11 13:36:45 DEBUG ChannelDataWindow: local window consumed 28 bytes of window space (130612 bytes left)
2018-11-11 13:36:45 DEBUG SshFxpStatus: ErrorCode|Status=0
2018-11-11 13:36:45 DEBUG SubsystemMessageStore: Received SSH_FXP_STATUS subsystem message
2018-11-11 13:36:45 DEBUG AsyncService: Finished processing SSH_MSG_CHANNEL_DATA
2018-11-11 13:36:45 DEBUG SshMessageStore: Waiting for max 30000 ms
2018-11-11 13:36:45 DEBUG SftpSubsystemClient: Received response
2018-11-11 13:36:45 DEBUG SftpClient: put(/Users/j.wierda/home/vpftptest/data/ftpqueue_in/P5L.MGL.KLACHTAFHANDELING/20181109_MGL_AFH_005707.XML,20181109_MGL_AFH_005707.XML)
2018-11-11 13:36:45 DEBUG SftpSubsystemClient: getAttributes('/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML')
2018-11-11 13:36:45 DEBUG SubsystemChannel: Sending SSH_FXP_STAT (path=/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML,id=7)
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sending 4 bytes for channel id 0 (maxSize=32648)
2018-11-11 13:36:45 DEBUG ChannelDataWindow: remote window consumed 4 bytes of window space (4294967172 bytes left)
2018-11-11 13:36:45 DEBUG TransportProtocolCommon: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
2018-11-11 13:36:45 DEBUG TransportProtocolOutputStream: Sent message. Seq no=19, msg=94
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sent 4 bytes (4 total) for channel id 0
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sent total bytes 4 for channel id 0
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sending 50 bytes for channel id 0 (maxSize=32648)
2018-11-11 13:36:45 DEBUG ChannelDataWindow: remote window consumed 50 bytes of window space (4294967122 bytes left)
2018-11-11 13:36:45 DEBUG TransportProtocolCommon: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
2018-11-11 13:36:45 DEBUG TransportProtocolOutputStream: Sent message. Seq no=20, msg=94
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sent 50 bytes (50 total) for channel id 0
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Sent total bytes 50 for channel id 0
2018-11-11 13:36:45 DEBUG TransportProtocolCommon: Received registered message: Name=SSH_MSG_IGNORE,MessageId=2
2018-11-11 13:36:45 DEBUG TransportProtocolCommon: Received unregistered message: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
2018-11-11 13:36:45 DEBUG AsyncService: Routing SSH_MSG_CHANNEL_DATA
2018-11-11 13:36:45 DEBUG ConnectionProtocol: Received 38 bytes of data for channel id 0
2018-11-11 13:36:45 DEBUG ChannelDataWindow: local window consumed 38 bytes of window space (130574 bytes left)
2018-11-11 13:36:45 DEBUG SshFxpStatus: ErrorCode|Status=2
2018-11-11 13:36:45 DEBUG SubsystemMessageStore: Received SSH_FXP_STATUS subsystem message
2018-11-11 13:36:45 DEBUG AsyncService: Finished processing SSH_MSG_CHANNEL_DATA
2018-11-11 13:36:45 DEBUG SshMessageStore: Waiting for max 30000 ms
2018-11-11 13:36:45 DEBUG SftpClient: put(remote path=/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML, append=false,resume=false)
2018-11-11 13:36:45 DEBUG SftpSubsystemClient: getAttributes('/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML')
2018-11-11 13:36:45 DEBUG SubsystemChannel: Sending SSH_FXP_STAT (path=/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML,id=8)

1 Answer

0 votes
answered by (43.9k points)
selected by
 
Best answer
No, there's no chance that edtFTPnet/PRO is creating a folder as a side-effect of uploading a file.  It's likely that there's some special functionality on the server that causes this behaviour.
commented by (150 points)
Thanks, if I look at the first log I see
2018-11-11 13:18:17 DEBUG SftpClient: put(remote path=/TMGDKLACHTEN/20181109_MGL_AFH_005707.XML/20181109_MGL_AFH_005707.XML, append=false,resume=false)

At this point an extra folder is in the path.
How does edtFTPJ-pro determines this path?
Is there a way to trace the response of the target server?
Although the logging is already extensive, somehow I want to prove that this path is provided as a response from the server.
Thanks in advance.
commented by (43.9k points)
edtFTPj/PRO logs a message starting with "Make directory" when it creates a directory, so if you don't see that message then it's not creating a directory.  Looking at the client in order to diagnose an issue on the server seems like asking for trouble.  Can't you either look in the server logs yourself or ask the server admins to explain the behaviour?
...