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

======================================================================

Closed Issues in 5.4.2_hotfix09 (This Release)

1-8WHAAJ
When one class was declared as a class member of the other and both
classes had the same getter/setter methods, the Java to XML activity
failed to distinguish the getter and setter methods between the two
classes. This has been fixed by adding a design-time property
'com.tibco.bw.plugin.java.java2xml.multischema'. Set this property to
true in designer.tra to support namespace multischema mode. By default,
the single namespace schema mode is supported.
You must install TIBCO Runtime Agent 5.5.4_hotfix07 to avail this fix.
If the design-time property is set and the TIBCO Runtime Agent
5.5.4_hotfix07 is not installed, a 'MultiSchemaNotSupportedException'
is thrown while generating the schema.

1-9CVZKG
Type coercion for AE subscriber plugins failed if the child schema had
a sequence or union. This has been fixed.

1-9CXT9N
The Publish to Adapter activity with a Request/Reply failed to receive
the response if the response had a child class and the Publish to
Adapter reply schema pointed to the parent class. This has been fixed.
Note that after applying this fix, the Publish to Adapter activity will
not validate the output data.

1-9DZ1Z6
The Timer activity did not adjust the Daylight Saving Time when the
timer interval was specified in any unit other than 'days' and the
interval was equal to or more than one day. This has been fixed.

1-9KR8KR
When the Service resource received a malformed SOAP over JMS message,
a NullPointerException was thrown on the console and all subsequent
incoming SOAP over JMS messages, including the well-formed ones, were
blocked. This has been fixed.
You must install TIBCO Runtime Agent 5.5.1_hotfix03 to avail this fix.

======================================================================
Closed Issues in 5.4.2_hotfix08

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

======================================================================
Closed Issues in 5.4.2_hotfix7

1-94QT21
An error occurred when using the JDBC activities to invoke a DB2
stored procedure on OS/390. This has been fixed by introducing a
property, 'java.property.Config.JDBC.DB2.CallProcedure.Mainframe'.
By default, this property is set to false. Set this property to true
to use the JDBC Call Procedure activity to invoke a DB2 stored
procedure on OS/390.

=====================================================================
Closed Issues in 5.4.2_hotfix6

1-8MHYJL
When an optional element is mapped to another element by using the
Copy and Paste options to copy the formula, the cardinality of the
optional element changed from 'Optional' to 'Required'. This has
been fixed.

1-8MHYK6
When values of mapped elements were changed and the changes were
applied, all mapped elements except the last one disappeared. This
has been fixed.
  
1-8YH4TF
When an ActiveEnterprise Invoke an Adapter Request Response Service
activity times out, the objects in memory were not released and
eventually the BusinessWorks engine threw an OutOfMemoryError. This
has been fixed.
  
1-908F9S
The global variables values could not be caught by the Catch
activity when the property EnableMemorySavingMode was set to true.
This has been fixed.
  
======================================================================
Closed Issues in 5.4.2_hotfix5

1-8V4OF3
For a JDBC XA Connection to Oracle RAC using the TIBCO driver, the
Database URL did not accept the attributes, ServiceName, and
AlternateServers. This has been fixed. These attributes can be
specified in the Database URL using the following syntax -
jdbc:tibcosoftwareinc:oracle://&lthost1>:&ltport1>ServiceName=
&ltdb_instancename>AlternateServers=(&lthost2>:&ltport2>,&lthost3>:&ltport3>,
...,&lthostN>:&ltportN>)

1-8WXELX
As a result of the fix for 1-8EGZZ0 in TIBCO BusinessWorks 5.4.2,
the "dataEncipherment" KeyUsage flag was not required and user
certificates had to have only "digitalSignature" and
"keyEncipherment" KeyUsage attributes. This caused the third party
applications to fail with a "PKA Decrypt failure" error when
confidentiality policy was used. This has been fixed.
TIBCO BusinessWorks now requires the user certificate to have
"dataEncipherment" KeyUsage flag in addition to "digitalSignature"
and "keyEncipherment" KeyUsage attributes.

1-8WXN2D
The Parse Data Activity can only parse a maximum of two optional
fields at the end of each line that has a "Fixed" Format. This has
been fixed.

1-8VT2JO
On Linux, when a process having a series of JDBC Query activities to
Sybase is run with multiple parallel jobs, some jobs get completed
only when all the other jobs are completed. This has been fixed.

To fix this, set the bw.plugin.jdbc.checkClosed property to false.
This property is set to true by default.

1-8YN00B
The SOAPRequestReply activity did not support type substitution in
the detail element of the SOAP Fault message. This has been fixed.  

======================================================================
Closed Issues in 5.4.2_hotfix4

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.

======================================================================
Closed Issues in 5.4.2_hotfix3

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 failed 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 French 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.

======================================================================
Closed Issues in 5.4.2_hotfix2

1-8DO1O0
The 'Attribute of Type' option in the Input/Output Editor tab of
activities was not available from BusinessWorks version 5.3 and
above. This has been fixed.

======================================================================
Closed Issues in 5.4.2_hotfix1

1-8E7S4A
SOAP Request Reply activity put wrong namespace in xsi:type when
elements of type Array were used. This has been fixed.

1-8ETT3S
TIBCO BusinessWorks always set 'selectMethod=Cursor' in the
Database URL while creating a JDBC Connection for MS SQL. Hence,
the user was never able to use 'selectMethod=Direct' in the Database
URL. This has been fixed by introducing a plugin property,
bw.plugin.jdbc.mssqlEnforceSelectmethodToCursor. The default value
for the property is true. If this property is set to false,
BusinessWorks does not enforce 'selectMethod=Cursor' and uses the
selectMethod set in the Database URL. If the selectMethod is not
set, the Data direct driver default, selectMethod=Direct, is used.

1-8FK3L4
When the 'Use Shared JMS Connection' checkbox in the SOAP Request
Reply activity is selected, the connection information (such as
Username and Password) of the shared JMS connection resource has to
be used. Instead, the connection information was being picked up
from the values specified in the transport details tab of the SOAP
Request Reply activity. This has been fixed.

1-8GHN5X
When parameters were specified with a higher precision, the JBDC
Call Procedure activity threw a ClassCastException. This has been
fixed.

1-8HSSJT
Audit logs for WSS authentication using X509 certificates were not
available in TIBCO BusinessWorks. This has been fixed. TIBCO
BusinessWorks now logs messages in the following format -
"Authentication attempt [principal=%1,authentication_succeeded=%2]"
where, %1 is the subject DN and %2 is the outcome of the
authentication attempt.

1-8I5MKV
When using SOAP over JMS, SOAP Request Reply activity was unable to
process SOAP Fault messages. This has been fixed.  

======================================================================