Closed Issues in 6.1.0_HF-006 (This Release)
BC-8398
When BusinessConnect generated EDI Acknowledgement such as TA1 which sit in Inbox
waiting to be downloaded by the trading partner through SFTP transport, the
trading partner failed to download it if BusinessEvent integration was enabled so
all the advisories were to be sent to BusinessEvent channels.
BC-8395
When multiple transactions with the same transaction ID were staged in Inbox waiting
to be downloaded by a trading partner, the trading partner was not able to download
these documents via FTPS, SFTP or TIBCO PartnerExpress.
BC-8387
BusinessConnect system property "bc.http.client.expect.header" which, when set to
"false", was used to exclude the "Expect: 100-conginue" HTTP header in outbound
HTTP requests when communicating to a server that only supports HTTP 1.0, didn't
take effect for outgoing AS2 asynchronous MDN receipt; the header still existed
in the MDN receipt which caused the MDN receiver side (the HTTP server)
mal-functioned.
(Set this property in TIBCO Administrator: BusinessConnect > System Settings >
Activated Protocol Plug-ins and Properties > BC.)
BC-8380
When using BusinessConnect as SSHFTP client to connect to an SSHFTP server on some
specific operating systems such as Microsoft Windows 2008 Server, BusinessConnect
failed to connect to the SSHFTP server and the following error occurred:
"SSHFTP An I/O error detected: SshMgr: Ssh Transport creation failed due to I/O
errors: Invalid argument: no further information".
This issue was fixed. Customer need to add this property in BusinessConnect engines'
.tra file to resolve this issue:
java.property.<trading partner name>.sshftp.tcpnodelay=false
BC-8379
BusinessConnect Gateway Server stopped responding to HTTP requests sent from trading
partners after running a long period of time due to memory leak.
BC-8368
When selecting password as the authentication mode to connect to an SSHFTP server
that works in keyboard-interactive mode, an "Authentication methods have been
exhausted: password" error occurred.
An extra option "Keyboard-Interaction" is added to the Authentication Mode
in the configuration of SSHFTP transport; the issue is fixed if you use this mode
rather than the "Password" mode to connect to the SSHFTP server.