Hi, for our latest product release, we bump our library from edtFTPjPRO_5.2.4 to edtFTPjPRO_7.2.3. We then started seeing issues when downloading the file from Maverick_SSHD file server. Debug logging shows successful handshake, change of directory, file listing, opening and reading the file. It looks like it is failing when the library tries to close the file (SSH_FXP_CLOSE). Note that we don't have any code changes, we just bump the library version.
Debug logging of working edtFTPjPRO_5.2.4
(com.enterprisedt.TransportProtocolCommon) Local identification: SSH-2.0-edtFTPjPRO_5.2.4
(com.enterprisedt.TransportProtocolCommon) Read: 'SSH-2.0-Maverick_SSHD
. . .
(com.enterprisedt.SftpSubsystemClient) Closing file /DTDCA/12523_2023051211_09_27am.aba.PROCESSED.ACK.pgp
(com.enterprisedt.SubsystemChannel) Sending SSH_FXP_CLOSE (id=16)
(com.enterprisedt.ConnectionProtocol) Sending 4 bytes for channel id 3 (maxSize=32648)
(com.enterprisedt.ChannelDataWindow) remote window consumed 4 bytes of window space (130553 bytes left)
(com.enterprisedt.TransportProtocolCommon) Name=SSH_MSG_CHANNEL_DATA,MessageId=94
(com.enterprisedt.TransportProtocolOutputStream) Sent message. Seq no=38, msg=94
(com.enterprisedt.ConnectionProtocol) Sent 4 bytes (4 total) for channel id 3
(com.enterprisedt.ConnectionProtocol) Sent total bytes 4 for channel id 3
(com.enterprisedt.ConnectionProtocol) Sending 29 bytes for channel id 3 (maxSize=32648)
(com.enterprisedt.ChannelDataWindow) remote window consumed 29 bytes of window space (130524 bytes left)
(com.enterprisedt.TransportProtocolCommon) Name=SSH_MSG_CHANNEL_DATA,MessageId=94
(com.enterprisedt.TransportProtocolOutputStream) Sent message. Seq no=39, msg=94
(com.enterprisedt.ConnectionProtocol) Sent 29 bytes (29 total) for channel id 3
(com.enterprisedt.ConnectionProtocol) Sent total bytes 29 for channel id 3
(com.enterprisedt.SftpSubsystemClient) Waiting for response
(com.enterprisedt.TransportProtocolCommon) Received unregistered message: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
(com.enterprisedt.ConnectionProtocol) Received 44 bytes of data for channel id 3
(com.enterprisedt.ChannelDataWindow) local window consumed 44 bytes of window space (123642 bytes left)
(com.enterprisedt.SshFxpStatus) ErrorCode|Status=0
(com.enterprisedt.SubsystemMessageStore) Received SSH_FXP_STATUS subsystem message
(com.enterprisedt.SshMessageStore) Waiting for max 30000 ms
(com.enterprisedt.SftpSubsystemClient) Received response
(com.enterprisedt.SSHFTPClient) getFileListing(.)
Debug logging of not working edtFTPjPRO_7.2.3
(com.enterprisedt.TransportProtocolCommon) Local identification: SSH-2.0-edtFTPjPRO_7.2.3
(com.enterprisedt.TransportProtocolCommon) Read: 'SSH-2.0-Maverick_SSHD
. . .
(com.enterprisedt.SftpSubsystemClient) Closing file /DTAUACIN/20230510.BAI.pgp
(com.enterprisedt.SubsystemChannel) Sending SSH_FXP_CLOSE (id=15)
(com.enterprisedt.ConnectionProtocol) Sending 33 bytes for channel id 396 (maxSize=32648)
(com.enterprisedt.ChannelDataWindow) remote window consumed 33 bytes of window space (130635 bytes left)
(com.enterprisedt.TransportProtocolCommon) Name=SSH_MSG_CHANNEL_DATA,MessageId=94
(com.enterprisedt.TransportProtocolOutputStream) Sent message. Seq no=22, msg=94
(com.enterprisedt.ConnectionProtocol) Sent 33 bytes (33 total) for channel id 396
(com.enterprisedt.ConnectionProtocol) Sent total bytes 33 for channel id 396
(com.enterprisedt.SftpSubsystemClient) Waiting for response
(com.enterprisedt.TransportProtocolCommon) Received unregistered message: Name=SSH_MSG_CHANNEL_DATA,MessageId=94
(com.enterprisedt.ConnectionProtocol) Received 175 bytes of data for channel id 396
(com.enterprisedt.ChannelDataWindow) local window consumed 175 bytes of window space (114757 bytes left)
(com.enterprisedt.SshFxpStatus) ErrorCode|Status=4
(com.enterprisedt.SubsystemMessageStore) Received SSH_FXP_STATUS subsystem message
(com.enterprisedt.SshMessageStore) Waiting for max 30000 ms
(com.enterprisedt.SftpSubsystemClient) Received response
(com.enterprisedt.SftpClient) get(/DTAUACIN/20230510.BAI.pgp) failed
Extra information
- Our testing parameters are pretty much identical (credentials, same box, etc). Aside, of course, from the library version.
- There is a proxy server running on the client server. We configured both testing to use it.
- We are able to upload files (on the same FTP server) using the same parameters and both library versions.
- WinSCP can also download the file.
Let me know if you need any more information.
