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-03/  to download the appropriate hotfix for your OS/platform.

Closed Issues in 5.4.2_hotfix3 (This Release)



  1-87VYEC

  When using SOAP over JMS, SOAP Request Reply activity was unable to

  process SOAP Fault messages. This has been fixed.



  1-8HUPYU

  Adapter Subscriber activity falied to process a message if the

  classname contained an underscore (_). This has been fixed.



  1-8IJGKF

  If one of the calls to DriverManager to fetch a connection was

  delayed, the rest of the calls to fetch other connections to any

  database got blocked. This has been fixed by providing an option to

  create connections using DataSource instead of DriverManager. Two

  new properties have been added to address the issue.

  For databases supported by the product, set the

  "bw.plugin.jdbc.connection.useDatasource" property to true to create

  connections using the DataSource. This property is false by default.

  For custom database drivers, in addition to the above property, set

  the “bw.plugin.jdbc.customDSClass.&ltDriverName> = &ltDataSourceName>”

  property, where &ltDriverName> is the custom database driver name and

  &ltDataSourceName> is the custom database driver class name.



  1-8IJIJV

  When using SOAP over JMS with Acknowledgement Mode set to Client,

  job creation was not limited by the value of Max Sessions. Also,

  when the first job was acknowledged, all the messages in the queue

  were lost. This has been fixed.



  1-8JO67L

  The SOAP Response message lost its encoding when the SOAP body

  for the input or output of a SOAP Request Reply activity contained

  special characters and the "Text Message" message format was used.

  The special characters include Latin characters and the Frech accent

  characters. This has been fixed.



  1-8JRXSV

  When the default namespace was used to refer to the namespace, such as

  &ltEnvelope xmlns="http://www.w3.org/2003/05/soap-envelope">, the SOAP

  Request Reply activity threw an exception. This has been fixed.



  1-8KOSEU

  When a bridge between a topic and multiple queues was defined and

  one of the queues had the queue size defined, if the queue size

  reached that limit, the other queues got multiple copies of

  messages. This has been fixed by introducing a new property,

  com.tibco.plugin.jmsSender.retryCount. Setting this property to zero

  ensures that the messages are sent only once.



  1-8MP2KJ

  SOAP Request Reply activity failed with an exception when the global

  variable BW_GLOBAL_TRUSTED_CA_STORE was defined in a BusinessWorks

  project but was not necessarily used in the confidentiality policy

  palette. The problem occurred when the confidentiality policy was

  set up for outbound. This has been fixed.

  

  1-8Q929B

  A Null Pointer Exception was thrown in com.tibco.pe.core.JobPager.

  This issue showed up in stressed environments and was associated

  with frequent job paging in combination with activationLimit

  property set to false. This has been fixed.



  1-8QRHHL

  When detailed tracing was turned ON and one of the JDBC activities

  blocked, all the other JDBC activities were also blocked. This has

  been fixed.