Description:
Hotfixes are cumulative. This hotfix includes all previous hotfixes

for TIBCO BusinessWorks 5.4.2.
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-04/  to download the appropriate hotfix for your OS/platform.

Closed Issues in 5.4.2_hotfix4 (This Release)



  1-6XG1DF

  When a JMS activity inside a Repeat Until group timed out and quit

  the loop, the associated JMS session was not released. This resulted

  in a large number of open sessions over a period of time. This

  problem was observed with the JMS activities such as Get JMS Queue

  Message, JMS Queue Sender, and so on. This has been fixed.



  1-7ZF6LM

  SOAP Fault messages with message part of type ‘type’ were wrapped

  under ‘partname’ element. Due to this, Fault messages with multiple

  child elements under the ‘details’ element could not be constructed.

  This has been fixed by introducing a new property,

  ‘bw.plugin.soapfault.detail.allowmultiplechildren’. To maintain

  backward compatibility, the default value of property is set to

  'false'. Set this property to true to handle multiple direct child

  elements under the element 'detail'.



  1-82HZ17

  For WSS Authentication policy using X509 token, if the token

  contained a self-signed certificate, the authentication succeeded

  even if the self-signed certificate was not present in the

  trusted folder. This has been fixed.



  1-85O3HS

  When the BusinessWorks engine was started in the command mode, the

  property 'bw.engine.showInput=true' did not work as expected. This

  has been fixed. Note that setting this property to true affects

  the performance as the input of all activities for every message

  is traced. It is recommended that you use this property only in

  test or debug environments.



  1-8MTE4Z

  When the Get JMS Queue Message activity with a dynamic destination

  was used in a loop and the number of messages received exceeded the

  queue prefetch value, the activity stopped without an error message.

  Also, the messages remaining in the queue were not confirmed. This

  has been fixed.



  1-8SF2CH

  The SOAPSendFault activity returned a Null Pointer Exception when

  the input data of "anyType" was substituted. This has been fixed.



  1-8V5PC9

  Whenever an exception occurs in JMS, TIBCO BusinessWorks checked

  for the validity of the connection which resulted in creating a

  session that was never closed. The situation aggravated when MQ JMS

  server was used as it created a JMS connection for every session

  and the session was never closed. This has been fixed.



  1-8V5PHK

  While retrying, the JMS Sender activity did not propagate the

  final exception that it encountered. As a result, the Catch

  activity did not catch the exception. This has been fixed.