on 09-18-2019 3:37 PM
Hi guys,
I used the SFTP adapter to send data to SFTP server.
When we test it with several thousand records, got a strange problem, that is:
after message mapping, I could see the file content is well; however, the file content is not correct
in the target sftp server, about every one thousand records, generating one line of unreadable record.
Would you like to help me out?
Can you figure out which version of the JSch library is used in the SFTP adapter? Up to version 0.1.52 there was a bug, which sounds like the behaviour you're experiencing.
From the changelog (http://www.jcraft.com/jsch/ChangeLog😞
"[...] [bugfix] sftp-put may send the garbage data in some rare case. [...]"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Just to be sure can you also do one more test, try with receiver file channel rather than sftp channel and place file in nFS directory and see if you get the same characters or good result.
Regards,
Vikas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What is your encoding and are you using FCC?
Thanks
Sugata
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sugata,
We use UTF-8 encoding, and even without FCC( convert it into the target format in Message Mapping step), the result is the same.
From below screenshot of source content, you can see that, there is no special language character set.
I had done another two test action:
1. With the same test data, before the data being sent, I delete the first 1100 records.
The result is that it is at line 1117, the same line as without deleting.
2. I download file content from the log of AM step, and upload it to SFTP server with tool FileZilla, and download it with chrome browser.
The result is the file content is correct.
**********updated on 20190920
Newly test, I can put the test data to the sftp server correctly in message mapping step via Java coding to call to SFTP server directly.
So, from the test, I can figure out that, it was not the SFTP server or network, but the SFTP adapter causing such an issue.
The release version of PO we are using is NW750EXT_11_REL.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.