Description:
You can download this HotFix 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/ActiveEnterprise/TIBCORuntimeAgent/5.5.2/hotfix-10/

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

======================================================================
Closed Issues in 5.5.2-hotfix10 (This release)

1-96MRX9
An application that used a message filter for an Adapter did not deploy
correctly in TIBCO Administrator 5.4.
This has been fixed

======================================================================
Closed Issues in 5.5.2-hotfix9

1-936V01
When millions of subscriptions existed in a domain, actions such as
login which accessed the subscription table in the domain database were
very slow; taking multiple seconds to complete.  Since such
accesses were processed one at a time, users experienced very long wait
times.

This has been fixed.

======================================================================
Closed Issues in 5.5.2-hotfix8

1-8YH7JB
The following issue has been fixed in the updated JDBC drivers:
* XA transaction could not be ended preventing transaction starts.

1-8ZH3AB
The following issue has been fixed in the updated JDBC drivers:
* Unsupported data conversion when fetching CLOB data from an
   outparameter.

======================================================================
Closed Issues in 5.5.2-hotfix7

1-8Y9C16
In the Java SDK, only two threads ran concurrently even when the adapter
created more than two threads for a JMS session. This has been fixed.

======================================================================
Closed Issues in 5.5.2-hotfix6

1-8U6370
JDBC driver in 5.5.2 did not work with SQL server 64 bit version
when using XA JDBC transactions. This has been fixed.

======================================================================
Closed Issues in 5.5.2-hotfix3

1-8HYVND
This fixed a security vulnerability.  For detailed information, please
contact TIBCO support.

1-8IKEOW
Authentication Plug-in Wrapper that provided Pre and Post Authentication
capability, forced the Authentication requests to be serialized. That
could cause performance degradation in situations where pre or post
autehntication was a lengthy process. This has been fixed and all the
user authentication requests (login, verify or logout) are now executed
in parallel.

======================================================================
Closed Issues in 5.5.2-hotfix2

1-8FOWZN
After release 5.5.2-hotfix1 was installed, TIBCO BusinessWorks would fail
to initialize SSL server sockets when attempting to filter restricted
ciphers.
This has been fixed.

======================================================================
Closed Issues in 5.5.2-hotfix1

1-6NYY58
When TIBCO PortalBuilder(TM) instantiated a large number of threads,
and each thread invoked the ExpandedName.makeName() method, all
threads remained waiting on ExpandedName.makeName() due to thread
contentions.
This has been fixed.

1-7ZRM41
TIBCO PortalBuilder showed notification messages that were not
localized.
This has been fixed.

1-88CTA9
When authenticating a self-signed certificate (root or leaf) from a
server, the software failed to verify the certificate's Common Name
against the server's hostname.
This has been fixed.

1-895KTU
After TIBCO BusinessWorks(TM) was migrated from release 5.1.3 to
release 5.2 or above, the Xpath function "parse-Datetime" added time
zone information at the end of the datetime string, which caused
release 5.4 or above to break backward compatibility with release  5.1.3.  
A system property "com.tibco.xml.xpath.parse-dateTime.has.timezone"
is added. The default value is "true". Setting to "false" gives behavior
consistent with BW 5.1.x.
This has been fixed.

1-8B1BXR
The software was not able to use the TLS_DHE_RSA_WITH_AES_128_CBC_SHA
cipher suite when using the non-default J2SE security provider.
This has been fixed.

1-8C0BOE
In release 5.5.2, when an application was redeployed in TIBCO
Administrator(TM), its global variables were reset to the values in
the EAR file that was loaded for redeployment.
This has been fixed.

1-8CZGKP
Updated the Entrust 7.2 security provider with Patch 134641, which was
validated as FIPS 140-2 compliant.

1-88XF09
Removed the synchronization on the LDAP Group object while checking
membership of a user in a certain (static or dynamic) group. This would
increase the performance during peak loads. Since multiple requests
for group membership were for different users, this would not add any
more LDAP requests.

1-86D040
ReaderWriterMonitor around Authorization check was not appropriate.
Any update would be locked out until Authorization checks were finished.
All new calls to Authorization checks after any update was made would
also be locked out. Therefore the ReaderWriterLocks were removed around
the Authorization checks. This would increase the performance during peak loads.
======================================================================