Closed Issues in 6.3.0_HF-002 (This Release)
BC-9091
When TIBCO BusinessConnect enabled DB lock mechanism and multiple Interior
Servers were deployed, TIBCO BusinessConnect occasionally failed to acquire
DB Lock in certain scenario while DB connection delay happened.
To resolve this issue, add the following property to the .tra files of
all the BusinessConnect interior servers:
java.property.bc.DBLock.strongMode.enable=true
BC-9089
If TIBCO BusinessConnect SOAP Protocol 6.1.0 was installed, TIBCO BusinessConnect
threw OutOfMemoryError when handling CMI transactions.
BC-9046
When PGP Processing was enabled for the inbound SSHFTP poller in Business
Agreement, TIBCO BusinessConnect did not pass the OriginalFileName field
correctly to the Private Process.
BC-9045
TIBCO BusinessConnect failed to calculate the key size of certain ciphers,
and as a result, TIBCO BusinessConnect did not support these ciphers
on AIX platform.
BC-9032
TIBCO BusinessConnect failed to send or cancel multiple transactions at a
time in Log Viewer > Message Queue Logs.
BC-9012
TIBCO BusinessConnect failed to connect certain SFTP servers with I/O errors
on Windows platform.
To resolve this issue, add the following property to
the .tra files of the BusinessConnect interior servers:
- To make this solution take effect for only one trading partner:
java.property.<trading partner name>.sshftp.tcpnodelay=false
- To make this solution take effect for all trading partners:
java.property.sshftp.tcpnodelay=false
================================================================================
Closed Issues in 6.3.0_HF-001
BC-8966
Cipher TLS_EMPTY_RENEGOTIATION_INFO_SCSV was disabled in TIBCO BusinessConnect.
BC-8959
TIBCO BusinessConnect did not allow SSLv2Hello protocol in Gateway Server.
There is a new property "bc.security.sslv2hello.enabled" added to Admin GUI
BusinessConnect -> System Settings -> Activated Protocol Plug-ins and Properties
-> BC after Initialize Database, it is unchecked by default. Gateway Server will
allow SSLv2Hello protocol if this property is checked.
BC-8954
BusinessConnect Gateway Server threw exception when start up if HTTP/S service was
only configured with "Secure CA Port" but not the "HTTP" and "HTTPS" port.
BC-8953
When PGP encryption was enabled for outbound SSHFTP transport, file mask which
contain #(DocumentID) did not work.
BC-8952
When stop BusinessConnect Gateway Server from TIBCO Administrator GUI, the HTTP/HTTPS
ports were not released by BusinessConnect Gateway Server services. To fix this issue,
add the following line to gsengine.tra files of all TIBCO BusinessConnect Gateway servers.
java.property.gs.webengine.socket.bindOnInit=false
BC-8951
TIBCO BusinessConnect did not support new property of NAESB 3.0 standard, such
as "receipt-security-selection", "refnum" and "refnum-orig".
There is a new property "GISB/NAESB Version" in HTTP/HTTPS transport, default value
is 2.0. if the value of this property is 3.0, TIBCO BusinessConnect will add "refnum",
"refnum-orig" and "receipt-security-selection" in outbound NAESB request.
BC-8942
TIBCO BusinessConnect failed to connect certain SFTP servers with I/O errors
from Windows platform. To resolve this issue, add the following property in
the .tra files of the BusinessConnect interior servers:
- To make this solution take effect for only one trading partner:
java.property.<trading partner name>.sshftp.tcpnodelay=false
BC-8909
When a schema in operation of BusinessConnect SOAP Protocol refer to other
schema imported by WSDL tool, it cannot be synchronized to Private Process via
BusinessConnect Palette.
BC-8906
TIBCO ActiveMatrix BusinessWorks Plug-in for BusinessConnect 6.0.1 failed to
import JMS transport settings with SSL configuration. This fix works with
TIBCO ActiveMatrix BusinessWorks Plug-in for BusinessConnect 6.1.0 and higher.
Note: Please copy configstore-core.jar and configstore-bc.jar of this
hotfix into {TIBCO_HOME}/bw/plugins/lib directory if TIBCO BusinessConnect
Palette 6.x was installed.
BC-8774
When multiple Interior Servers were deployed, if XML requests were sent with the
txnGroupingID field from private processes, TIBCO BusinessConnect occasionally
failed to add converted EDI transactions for batching and DBLock error occurred.