Description:
TIBCO BusinessConnect 5.3.3 hotfix 1 has been released.

You can download this Hot Fix from the TIBCO Product Support FTP server using your eSupport username and password, at

           ftp://support-ftp.tibco.com

Once you have successfully logged into the server, you will find the hotfix packages under

           available_downloads/ActiveExchange/BusinessConnect/5.3.3/hotfix-01/

Listed below is a summary of updates included. Please refer to the associated readme document for any additional information.

Closed Issues in 5.3.3 Hotfix 1 (This Release)

CR: BC-6175

Some FTPS servers cannot negotiate ssl transports in TLSv1 mode. In such a
case, BusinessConnect offers to restrict the frame version of the connection
to trading partners to SSLv3.

When using the property "java.property.bc.ftps.strictSsl3" to the engine's
TRA configuration file, there are three options:

a) when the property exists with no values, it means that any ftps connection
(outbound or poller), which specifies SSL for its transport property 'Secure
Transport Mode', will always use SSLv3 regardless of whether the server would
be able to promote the frame version to TLSv1.

b) when the property exists and has values in the form of "host1, host2, host3"
then the restricted SSLv3 connection will only apply to transports where the
peer hostname (ftps server) is in the list.

c) when the property does not exists then there is no change in behavior,
whereas an SSL setting in the transport property 'Secure Transport Mode' means
that the negotiation will result in either an SSLv3 or TLSv1 frameversion and
TLS means that the frame version will be either TLS or the connection fails if
the peer ftps server doesn't support TLSv1 communication.

Example:

java.property.bc.ftps.strictSsl3=www.partnerftps.com, 10.1.2.3

This setting restricts the ssl frame version to SSLv3 only for transports, whose
peers are www.partnerftps.com or 10.1.2.3 where the 'Secure Transport Mode' property
is set to SSL. All other transports will behave without any restrictions on the
frame version.


CR: BC-6158

Under high load conditions with large number of request response operations,
intermittent failures to close the database statements properly may
occur and consumes all system resources over time that could eventually
result into an abnormal shutdown on the process engines. This problem has
been fixed.

Earlier before the fix, the database resultset was fetched as a stream,
but due to intermittent failures, the fetch is read fully and closed. To
maintain backward compatibility, a new system property is added with a value
of false not to read fully. The property needs to be added in each of the
deployed engine .tra file and the property to be added is

  java.property.bc.hibernate.useJDBCBinaryStream=false|true

A value of 'true' would let the database resultset to be read fully before
closing the resultset rather than using the Database's stream mechanism.

CR: BC-6157

With very large number of internal transports configured, the dmz boot
process can consume an excessive amount of memory. This problem has been
fixed.

CR: BC-6145

The processing of incoming XML documents can hang for an extensive amount
of time if the document contains a leading BOM (byte-order-mark). This
issue is fixed.

CR: BC-6160

When there are thousands of Trading Partners with BusinessAgreements
for each of them, Administrator GUI response to show both the
Participants list and 'Business Agreements' list is very slow. The
fetching and rendering to show the list has been optimized to show the
list in a reasonable amount of time and this issue associated with the
slow response is fixed.

CR: BC-5555

The SSH transport did not allow for the maximum 4GB channel window size
but limited the size to 2GB. This problem has been fixed.

CR: BC-5553

The SSH transport did not handle some servers' lack of support for the
FSTAT command during operations of reading files from the server, which
resulted in failed transactions. This problem has been fixed.