This content has been marked as final. Show 3 replies
Why is Outbound working fine but Inbound not working at all?The log which you have posted above is for outbound transaction, not for inbound. Is there a firewall in between? If yes, then issue may be related to it. Are you able to manually ftp (get and put) to the target FTP server from your B2B machine? Also make sure that FTP user has read-write access in the polling directory.
Transport log in debug mode may provide some relevant information.
Yes, both are OUTBOUND processes. The 210 sends a file to the secured server using User/Password validation and works fine. The 997 is to retrieve a file from the same secured server using User/Password validation and does NOT work. The Transport Log in Debug mode gives only the following information. Both processes have the same Host/User/Password. The 210 has the Remote TP as the Responder. The 997 has the Host TP (Bennett) as the Responder. The HOST TP has a Wallet and Certificate setup for a AS2 process with a different client.
2013.02.22 at 11:07:14:342: B2BStarter thread: (DEBUG) initialize TransportReceiver: [BALT_AC_997_TS1 < sftp > < Bennett International Group >]
2013.02.22 at 11:07:14:342: B2BStarter thread: (DEBUG) SFTPReceiver init started ...
2013.02.22 at 11:07:14:910: Thread-14: (DEBUG) SFTP listener hasn't been active yet
2013.02.22 at 11:07:44:912: Thread-14: (DEBUG) SFTP listener hasn't been active yet
2013.02.22 at 11:08:14:914: Thread-14: (DEBUG) SFTP listener hasn't been active yet
2013.02.22 at 11:08:45:595: Thread-14: (DEBUG) Reinitiate connection as a result of TCP reset :
2013.02.22 at 11:10:46:027: Thread-14: (ERROR) The problem could be in the connection or file
com.maverick.ssh.SshException: Unexpected termination: Socket closed
at com.maverick.ssh2.TransportProtocol.sendMessage(Unknown Source)
at com.maverick.ssh2.A.A(Unknown Source)
at com.maverick.ssh2.Ssh2Channel.A(Unknown Source)
at com.maverick.ssh2.Ssh2Channel$_A.write(Unknown Source)
at com.maverick.ssh.SubsystemChannel$_A.A(Unknown Source)
at com.maverick.ssh.SubsystemChannel.sendMessage(Unknown Source)
at com.maverick.sftp.SftpSubsystemChannel.getAbsolutePath(Unknown Source)
at com.maverick.sftp.SftpSubsystemChannel.openDirectory(Unknown Source)
at com.sshtools.sftp.SftpClient.ls(Unknown Source)
What is the patch level of your system? A similar issue was fixed in MLR#12. You may raise a SR with support to figure out if you are facing a known issue and whether a patch is already available.