Description:
This hotfix doesn't need any TRA hotfix. The patch can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to /available_downloads/ActiveEnterprise/BusinessWorks/BW/5.4.2/hotfix-08/  to download the appropriate hotfix for your OS/platform.

Closed Issues in 5.4.2_hotfix08 (This Release)

1-7ZM2L9
In the Service palette, if the same service was configured using HTTP
and JMS endpoints, the concrete WSDL file generated had wsdl:prottype
declared twice. This has been fixed.

1-80FFXZ
The BusinessWorks engine Hawk microagent getStatus returned a
negative uptime value on the TIBCO Hawk display. This was observed
on the HP-UX platform. This has been fixed.

1-8XLZBN
If an Oracle RAC node switch occurred when under load, a message
duplication was observed. This has been fixed by introducing an engine
property 'bw.engine.transaction.RACXACompatibleMode'. By default, the
property is set to false. Set this property to true to enable the
fix and avoid message duplication. Note that setting the property to
true will affect the throughput.

1-8Y7W23
When the RAC node switch happened and the connection was established,
the SQL warning messages sent by the driver to the connection object  
were not getting logged. This has been fixed.

1-966TH9
Large number of transitions caused the engine to stall during startup
if the property EnableMemorySavingMode was set to true. This has been
fixed.

1-97HT1N
In case an operation had multiple faults configured, the SOAP client
checked for the first fault message and threw "Output data invalid"
error for any fault message other than the first one. This has been
fixed.

1-97XTP2
While sending back a SOAP fault for an internal error that occurred
while processing a message through a SOAP service agent configured
with JMS transport, the BusinessWorks engine always sent back SOAP 1.1
faults irrespective of the configured SOAP version in the SOAP service
agent. This has been fixed.

1-992LCF
Fixed a binding error associated with the SOAP Request Reply
activity.

1-9DJ7B7
The JDBC connections used in a JDBC transaction were not released
when an exception occurred during a rollback. This has been fixed
to release the JDBC connections and then propagate the exception.

1-9D0TP1
When an AE/JMS response message had an error associated with it,
the AE Request-Response activity failed with an Exception and took the
error path as expected. However, a memory growth in the engine is
noticed. This has been fixed