Closed Issues in 6.2.0_HF-002 (This Release)
BC-8443
When importing one participant twice the contacts information of this participant
was duplicated rather than merged.
BC-8430
When TIBCO BusinessConnect was connecting to an SSHFTP server, if
you selected the password mode as the authentication mode to connect
to the SSHFTP server that was working in the Keyboard-Interactive mode,
the "Authentication methods have been exhausted: password" error was
displayed.
The Keyboard-Interaction mode is added to the authentication mode in
the configuration of the SSHFTP transport; this issue is fixed if you use
the Keyboard-Interaction mode rather than the password mode to connect to
the SSHFTP server.
BC-8429
When EDI Acknowledgement such as TA1 was generated by TIBCO BusinessConnect
and was waiting in Inbox to be downloaded, if BusinessEvent integration was
enabled and all the advisories were to be sent to BusinessEvent channels, the
trading partner failed to download EDI Acknowledgement through the SFTP transport.
BC-8428
Because of a memory leak, TIBCO BusinessConnect Gateway Server stopped
responding to HTTP requests sent from trading partners after Gateway
Server was running for long time.
BC-8427
If the multiple transactions with the same transaction ID were staged in Inbox
waiting to be downloaded by a trading partner, the trading partner failed
to download these documents through the FTPS, SFTP, or TIBCO PartnerExpress.
BC-8426
If using TIBCO BusinessConnect as an SSHFTP client to connect to an SSHFTP
server on some specific operating systems such as, Microsoft Windows 2008
Server, TIBCO BusinessConnect failed to connect to the SSHFTP server and
the following error was displayed:
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. To resolve this issue, add the following property
in the .tra file of the BusinessConnect engines:
java.property.<trading partner name>.sshftp.tcpnodelay=false
BC-8425
When TIBCO BusinessConnect was communicating with a server that only supported
the HTTP 1.0 protocol, if the value of the "bc.http.client.expect.header"
BusinessConnect system property was set to false and excluded the "Expect:
100-continue" HTTP header in the outbound HTTP requests, the header still
existed in the outgoing AS2 asynchronous MDN receipt, which caused the
malfunction of the MDN receiver side (the HTTP server).
Set the bc.http.client.expect.header property in TIBCO Administrator:
BusinessConnect > System Settings > Activated Protocol Plug-ins and
Properties > BC.
BC-8423
If you were using TIBCO PartnerExpress with TIBCO BusinessConnect 6.2.0,
trading partners failed to access PartnerExpress Server from the client
side because the ClassCastException exception was thrown on the
server side.
BC-8422
When Gateway Server started a PartnerExpress service for the first time,
if you were using TIBCO PartnerExpress with TIBCO BusinessConnect 6.2.0,
the server threw a FileNotFoundException exception, which had no
influence on your operation.
BC-8421
Because of a memory leak, TIBCO BusinessConnect Gateway Server stopped
responding to the downloading and uploading requests of SFTP or FTPS
sent from trading partners after Gateway Server was running for long
time.
BC-8399
TIBCO BusinessConnect failed to decompress the received EMAIL request
if the request was encrypted and compressed with attachments on responder
side.
BC-8391
TIBCO BusinessConnect failed to import a .csx file if JRE1.7.0_72-b14 was
installed in the same TIBCO_HOME directory with other TIBCO products, such
as TIBCO ActiveMatrix BusinessWorks 6.2.0 and TIBCO Runtime Agent 5.9.1.