book
Article ID: KB0092629
calendar_today
Updated On:
Description
Resolution:
We have found a problem with TIBCrypt.jar that is bundled with this TRA 5.5.2 hotfix 1 and hence removing this hotfix from distribution. We are actively working on release a new hotfix, i.e TRA 5.5.2 hotfix 2 by next week (before Sept 8th 2007).
Meantime, if you would like to continue using TRA 5.5.2 hotfix 1 that you may have downloaded for the following defects:-
********************************************************
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-8C0BOE
In release 5.5.2, when an application is 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-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-88XF09
Removed the synchronization on the LDAP Group object while checking
membership of a user in a certain (static or dynamic) group. This will
increase the performance during peak loads. Since multiple requests
for group membership are for different users, this will not add any
more LDAP requests.
1-86D040
ReaderWriterMonitor around Authorization check is not appropriate.
Any update will be locked out until Authorization checks are finished.
All new calls to Authorization checks after any update is made will
also be locked out. Therefore the ReaderWriterLocks are removed around
the Authorization checks. This will increase the performance during peak loads.
**********************************************************
you may do so by removing TIBCrypt.jar that is present in <TIBCO_HOME>/tra/5.5/hotfix/lib directory.
Issue/Introduction
TIBCO Runtime Agent (aka TRA) 5.5.2 Hotfix 1 has been REVOKED