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.2.1/hotfix-14

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

======================================================================
Issues Closed in 5.2.1-hotfix14 (This release)

1-8H1WG0
In Java SDK, when using the RPC Server service, the JMS session did
not close properly. This has been fixed.

1-73A7CS
In C++ SDK for JMS transport, connection factory lookup was always done and this broke the backward
compatiblity. There was no way to enable or disable the connection factory lookup.

A new property, tibco.connectionfactorylookup, has been added:
tibco.connectionfactorylookup = "on"/"off"
By default, the property is set to off for backward compatibility.

======================================================================
Issues Closed in 5.2.1-hotfix13

1-83L787
wrap has been recompiled on the HP-UX PA-RISC platform
so that the operating system can allocate more memory to running
processes.

To make use of this fix, copy and rename the wrap file to replace one
or more of following executables:

* &ltTIBCO_HOME>/tra/5.2/bin/*
* &ltTIBCO_HOME>/designer/5.2/bin/*
* Product-specific executables, such as &ltTIBCO_HOME>/bw/5.2/bin/*
* administration domain specific executables, such as
   &ltTIBCO_HOME>/administrator/5.2/bin/tibcoadmin_&ltDOMAIN> or
   &ltTIBCO_HOME>/tra/domain/&ltDOMAIN>/hawkagent_&ltDOMAIN>

======================================================================
Issues Closed in 5.2.1-hotfix12

1-7T31CY (TIBCO Runtime Agent)
This hotfix contains the DataDirect 3.6 drivers that are required for
Oracle 10g R2 (10.2.x.x).

======================================================================
Issues Closed in 5.2.1-hotfix11

1-1AT61T (TIBCO Adapter SDK)
On Windows 2003 Server, The value assigned to the TIB_ICU_DATA
environment variable in the adapter's .tra file was not picked up at
runtime. This has been fixed.

1-6T6HUN (TIBCO Adapter SDK)
On Windows XP, an error would result when publishing Japanese
language data using SHIFT-JIS as the encoding value. This has been
fixed.

1-6VWI7T (TIBCO BusinessWorks)
An SQL statement could not be executed using SQL DIRECT in TIBCO
BusinessWorks. This has been fixed.

======================================================================
Issues Closed in 5.2.1-hotfix10

1-6SJXK9 (TIBCO Adapter SDK)
For multithreaded adapters, high CPU use would result when a JMS
connection was lost even there was no incoming requests. This has
been fixed.

1-6TMU9D (TIBCO Adapter SDK)
The space of a reply parameter (of MBinary type) was freed during a
syncInvoke call, so when the reply parameter was accessed a free
memory error occurred. This has been fixed.

======================================================================
Issues Closed in 5.2.1-hotfix9

1-6B2E3I (TIBCO Designer)
When using CVS, a folder rename in TIBCO Designer had no effect with
the CVS server repository. This has been fixed.

======================================================================
Issues Closed in 5.2.1-hotfix8

1-6S4T3G (TIBCO XML)
XML file validation would fail for decimal value .00. This has been
fixed.

======================================================================
Issues Closed in 5.2.1-hotfix7

1-1Z2N4O (TIBCO Adapter SDK)
When using an HTTP RepoURL, the C++ Adapter SDK was taking a long time
to fetch instance configuration data from the TIBCO Administrator
repository server. This has been fixed.

1-6RB2TB (TIBCO Adapter SDK)
The C++ Adapter SDK Base64 encoding of a binary message introduced
an extra character ('\n') in the message. As a result, message decoding
would fail on the Java subscriber side with a 'String index out of
range' exception. This has been fixed.

1-6SAA5H (TIBCO Administrator)
If a user was given read, write and admin privileges to a folder under
Application Management and attempted to configure an application
under that folder, the user could not:
* see the Service Instances console for the deployed application.
* add a machine to an archive.
* add monitoring events to an archive.
This has been fixed.

======================================================================
Issues Closed in 5.2.1-hotfix6

Defect 1-6Q32GB (TIBCO Runtime Agent)
The TIB_tra-suite_5.2.1_lnx86_24_323.tar package incorrectly included
Linux 7.2 files instead of the correct TPCL Linux Advanced Server 3.0
files. This has been fixed.

======================================================================
Issues Closed in 5.2.1-hotfix5

Defect 1-30TRLT (TIBCO XML)
Schema with "processContents = lax" did not catch the errors.
This has been fixed.

1-6OEC6J (TIBCO XML)
The WSDLBuilder did not handle AESchema that referred to other
AeSchema correctly. If the WSDLBuilder used an AESchema that
imported other AESchema, the generated WSDL did not embed the imported
AESchema correctly. This has been fixed.

======================================================================
Issues Closed in 5.2.1-hotfix4

Defect 1-67ZWSM (TIBCO Runtime Agent)
A close_notify alert sent by the Entrust server was not being
acknowledged by client programs. This resulted in too many client
sockets left open and the server running out of threads if a large
number of requests were received. This has been fixed.

Defect 1-6NH7R9 (TIBCO XML)
The conversion from an incoming message to an XI node would sometimes
return empty. This has been fixed.

======================================================================
Issues Closed in 5.2.1-hotfix3

Defect 1-4DJ3YD (TIBCO Designer)
If you saved and closed a project for an adapter configuration such
as TIBCO Adapter for MQSeries that contained a service, reopened the
project and changed the transport, then saved and closed the
project, the project would be corrupted when attempting to reopen it.
This has been fixed.

Defect 1-4MVOVE (TIBCO Designer)
When exporting a project to a dat file using TIBCO Designer 5.2, some
scalar elements were missing in the exported .dat file. As a result,
an adapter such as TIBCO Adapter for COM would not start. This has
been fixed.

Defect 1-5K6RWL (TIBCO Designer)
When using the XML Canon DAV Plug-in for TIBCO Designer 5.2, when no
change was made after checking out resources and then synchronizing,
the resources appeared as locked (non-editable). When a change was
made after checking out a resource and then synchronizing, only the
changed resource was editable and other resources were locked
(non-editable). This has been fixed.

Defect 1-5PB33C (TIBCO Designer)
When using the XML Canon DAV Plug-in for TIBCO Designer 5.2, after
synchronizing and checking in resources, then closing the project,
you could nor reopen the project. This has been fixed. Note that
this defect is related to defect 1-5K6RWL above.

Defect 1-5MX5YH (TIBCO Designer)
When using the XML Canon DAV Plug-in for TIBCO Designer 5.2 and adding
files or folders or importing a folder that contained files, when
deleting a file from TIBCO Designer and saving, a null pointer
exception occurred. This has been fixed.

Defect 1-5MX5YZ (TIBCO Designer)
When using the XML Canon DAV Plug-in for TIBCO Designer 5.2 and
opening a project from XML Canon and adding a library builder or
deployment descriptor, then building an EAR file, when saving an
error would result indicating that "somehow an unknown resource
has already been added". This has been fixed.

Defect 1-5PI9NW (TIBCO Designer)
When using the XML Canon DAV Plug-in for TIBCO Designer 5.2, a
project could be opened by a user who did not have permissions
for the project. This has been fixed.

Defect 1-6D3Q6H (TIBCO Adapter SDK C++ API)
When an Adapter SDK JMS queue subscriber was suspended and
activated again, messages pending in the JMS queue were not
delivered. This has been fixed.

Defect 1-6KLGK0 (TIBCO Adapter SDK C++ API)
When an adapter used an Adapter SDK AE operation that used the TIBCO
Enterprise Message Service, no reply message was received and a
time-out did not occur. This has been fixed.

Defect 1-6GABD5 (TIBCO Runtime Agent)
The TIBCOadaptermappers.jar file has been updated with the latest
adcom.xsd file.

Defect 1-6ILYCB (TIBCO XML)
Errors would result when adding multiple Java classes that inherited
from the same class. This has been fixed.

======================================================================
Issues Closed in 5.2.1-hotfix2

Defect 1-5RJMXP (TIBCO BusinessWorks FormBuilder)
Deployment would fail on machines that were not connected to the
Internet. This has been fixed.

Defect 1-60H3ZX (TIBCO Adapter SDK)
For adapters, an _SDK.ERROR.RPC.BADMSGFORMAT advisory error would
result for a JMS request that contained empty value elements for a
UTF-8 repository. This has been fixed.

Defect 1-4ZX52C (TIBCO Administrator)
When using TIBCO Domain Utility to set or change TIBCO Rendezvous
parameters used by TIBCO Hawk, an alias could not be used for the
service parameter. This has been fixed.

Defect 1-60ZWVL (TIBCO XML)
When using the JMS transport and a UTF-8 repository, a deserialization
error would occur if certain fields were empty. This has been fixed.

Defect 1-4RIZP3 (TIBCO XML)
The validator would report an error if nested sequences were in
a content model, even though the XML was valid. This has been fixed.

Defect 1-5KH9DH (TIBCO XML)
When configuring a Publish Rendezvous Message activity with the
Content specified as "Any Element" and the Validation to
"Skip", a NullPointerException resulted. This has been fixed.

======================================================================
Issues Closed in 5.2.1-hotfix1

Defect 1-5MLNKR (TIBCO Adapter SDK C++ APIs)
Specifying the JmsProviderURL with a pipe symbol resulted in an
exception with an invalid port error. JMS C APIs support load
balancing server URI specification only through ConnectionFactories,
which TIBCO Adapter SDK code was not using. This has been fixed.

The adapter JMS session configuration should simply provide the
connection factory name. The load balance url is taken care of by the
JMS server, which refers to factories.conf for the definition. The
JmsProviderURL on the adapter JMS session serves only to provide the
initial connection url.

Defect 1-5JB3YK (TIBCO Adapter SDK C++ APIs)
When a C++ Adapter set the HTTP based repoURL and tried to communicate
with READ-ONLY Administrator servers, it was throwing an exception.
This has been fixed.

Defect 1-5GVQ9N (TIBCO Adapter SDK C++ APIs)
An adapter would crash when receiving messages from a JMS Queue where
the integer type JMS property JMSXDeliveryCount was set. This has
been fixed.

Defect 1-5I6PB1 (TIBCO Adapter SDK C++ APIs)
When a repoURL encrypted password contained more than 66 characters
(prefixed by #!), an adapter would throw the error:
".\crypto\evp\evp_enc.c(261): OpenSSL internal error, assertion
failed: inl > 0". This has been fixed.

Defect 1-5UI0J9 (TIBCO Adapter SDK C++ APIs)
Temporary consumers were not correctly deleted in case of timeout.
This caused CPU utilization to go up even during idling. This
has been fixed.

Defect 1-5LMCRL (TIBCO Administrator)
The logout action did not work correctly for Web Server Authentication
and allowed an application to create a new Http session within the
same browser session. This has been fixed.

Defect 1-404M4H (TIBCO Designer)
A ClasscastException was thrown when you tried to export a full project
to an administrator server, with a name that already existed. This
has been fixed.

Defect 1-551CFE (TIBCO Wrapper)
The adapter exited on startup on Windows XP with Service Pack 2.
Windows popped up the error, "&ltadapter-app-name>.exe has encountered
a problem and will be closed". This has been fixed.

The updated wrap.exe and gwrap.exe is installed under the
{TIBCO_HOME}/tra/5.2/hotfix/bin directory. Replace the copy of the
existing adapter executable with wrap.exe and rename it with the name
of the old adapter executable.