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.4/hotfix-8

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

======================================================================
Closed Issues in 5.5.4-hotfix8 (This release)

Defect 1-A22TQV
The schema could not be loaded correctly when it contained the recursive
xs:extension definitions.
This has been fixed.

======================================================================
Closed Issues in 5.5.4-hotfix7

Defect 1-9CDY92
The Java To XML activity did not display class correctly. It stuck
in infinite loop displaying element.
This has been fixed.

Defect 1-9L4G7Q
In the Properties tab of a TIBCO XML canon project, the build number was
displayed incorrectly as in "1.2.0 ${build.number}".
This has been fixed.

======================================================================
Closed Issues in 5.5.4-hotfix6

Defect 1-9GHFAG
When logging into TIBCO eBusiness Applications, an error message
similar to the following appeared:
"Invalid fourth parameter to SWE service method 'ProcessCommand'".
This has been fixed.

Defect 1-9GRJ0G
When using a JMS queue as the transport type for publication and
subscription services, the multi-thread mechanism did not work well.
This has been fixed.

======================================================================
Closed Issues in 5.5.4-hotfix5

Defect 1-9ALWA4
The TIBCO BusinessWorks inbound security policy failed to validate
inbound SOAP messages during authentication or signature if the
certificate had a root CA with the Name Constraints X509v3 extension
marked as critical.
This has been fixed.

Defect 1-9CBP3M
The JDBC driver failed to accept data larger than 32KB if the data type
was CLOB.
This has been fixed.

======================================================================
Closed Issues in 5.5.4-hotfix4

Defect 1-7CGP5S
TIBCO BusinessWorks threw a validation error when xsi:type appeared on
the node defined as xsd:any.
This has been fixed.

Defect 1-8U5KPP
TIBCO BusinessWorks did not resolve xsi:type for the wildcard node
itself, but resolved the descendent nodes.
This issue has been fixed.

Defect 1-8UZCPL
One of the XML parsers in TIBCOxml did not properly handle the "tibco-char"
processing instruction, causing those special characters to disappear
after parsing.
This issue has been fixed.

Defect 1-88HNMX, 1-8WWXDH, 1-8YJ0AH, 1-92MAIP
When specifying XML type substitution in the SOAP response message, the
SOAP Service failed and the error message "Caused by: com.tibco.util.
RuntimeWrapException: Internal Error:" displayed.
This issue has been fixed.
======================================================================
Closed Issues in 5.5.4-hotfix3

Defect 1-8WRDTO
When using a DB2 database domain, deployment delays and failures
would result due to DB2 locks.
This issue has been fixed.

======================================================================
Closed Issues in 5.5.4-hotfix2

Defect 1-8ERPEK
The Render XML Activity throws IllegalCharsetNameException if an
encoding had been set, and then removed later.
This issue has been fixed.

Defect 1-8XJFU9
Global variables values are getting reset to default EAR values if
the global variable value is changed in TIBCO Designer(TM) after its
initial upload to the TIBCO Administrator(TM) UI.
This issue has been fixed.

Defect 1-8YG32X, 1-8Y0RST
With TIBCO Runtime Agent 5.5.4 WSS MOPS Entrust and MOPS JKS MEP
cases fail with "WS Security Error : 6".
This issue has been fixed.

Defect 1-8YJBSV
With TIBCO Runtime Agent 5.5.4 HotFix-01 userFactory.userExists(userId)
is always returning true.
This issue has been fixed.

Defect 1-8YXYIJ
Any Add/Delete operation on Membership of a Standard Role via API
is also checking if members of the Role are valid users.
This is causing a serious performance issue when a Role has large number
of users assigned as members.
This fix provides a further performance improvement over the earlier
fix for the defect 1-8X16LJ (in hotfix1).

======================================================================
Closed Issues in 5.5.4-hotfix1

Defect 1-8X16LJ
Any Add/Delete operation on Membership of a Standard Role via API
is also checking if members of the Role are valid users.
This is causing serious performance issue when a Role has large number
of users assigned as members.
This is fixed.

Defect 1-8X8G0U
Temporary topics are not getting deleted when tibrvjms transport is used.
This is fixed.