Runtime

This topic lists the Closed Issues related to Runtime.

Release 2.7.2

Key Summary
AMBW-44222 The module shared variable failed to reset to initial value on restarting an application.

Release 2.7.0

Key Summary
AMBW-44452 When migrating the TIBCO ActiveMatrix BusinessWorks application from 6.4.1 to 6.6.0, the JobsharedVariable defined in a module is not recognized by other modules of an application.
AMBW-44451 Two applications incorrectly refer to the same hashmap in some cases when an AppNode starts the applications at the same time, and an activator process is used along with custom XPath functions.
AMBW-44450 For Group mode, if the AppNodes are unresponsive for more than 31 seconds then the process starter activity is disabled for the AppNodes which results in AppNodes are marked as inactive by the recovery system..Set the com.tibco.bx.engine.recovery.failure.threshold property to a value between 31 to 180 seconds.
AMBW-43980

TIBCO ActiveMatrix BusinessWorks application containing the FTL Subscriber activity having flowlimit set along with engine threads displays the out of memory error when the number of transactions per second are increased above 50.
AMBW-43770 The JMS Receive Message activity running on an AppNode with the Group mode fails to start when a BWEngine resumes from the Suspended state.
AMBW-43221

The Wait and Notify activities in the group persistence mode do not work with default values for the bw.engine.threadCount and bw.engine.db.maxConnection properties.

Set the following new properties in the AppSpace's config.ini file: 

com.tibco.bx.lockWaitNotify=true
com.tibco.bw.throttle.notify.activity=true 
com.tibco.bw.throttle.wait.activity=true

Use the throttle properties when default configuration is used .

The bw.engine.db.maxConnection property's value must be greater than the bw.engine.threadcount value.
AMBW-43220

Some of the TIBCO BusinessWorks Container Edition jobs are not processed intermittently when an application has Wait and Notify activities.

To avoid the deadlock scenario, TIBCO recommends to set the com.tibco.bx.lockWaitNotify=true property and the value of bw.engine.db.maxConnection property = twice the value of bw.engine.threadCount.
AMBW-43102 On stopping the application, an application cannot call the delete method of the shared resource when the shared resource uses module property in one of the fields.
AMBW-43101 The BW.MODULE.NAME and BW.MODULE.VERSION module properties return empty values.
AMBW-43099 The Iterate group in a subprocess generates incorrect output when two different processes call the same subprocess containing the Iterate group at the same time.
AMBW-42919 After new installation and setup of AppSpaces and the AppNodes, the AppNodes that have "group" settings cannot start and display the following error: Unable to find CheckpointModelFactory: DB.
AMBW-42506 Modifications done inside a running application in TIBCO Business Studio for BusinessWorks displays the Process not found error.
AMBW-42106 AppNode APIs now provide complete stack trace in a thread dump.
AMBW-41286 TIBCO Business Studio for BusinessWorks throws NullPointerException while running a project with different nested subprocesses.

Release 2.6.2

Key Description
AMBW-43223

The Wait and Notify activities in the group persistence mode do not work with default values for the bw.engine.threadCount and bw.engine.db.maxConnection properties.

The following new properties are introduced in the AppSpace's config.ini file:

  • com.tibco.bx.lockWaitNotify=true

  • com.tibco.bw.throttle.notify.activity=true

  • com.tibco.bw.throttle.wait.activity=true

Use the throttle properties when default configuration is used.

The bw.engine.db.maxConnection value must be greater than the bw.engine.threadcount value.

AMBW-43222

Some of the TIBCO BusinessWorks Container Edition jobs are not processed intermittently when an application has the Wait and Notify activities.

To avoid the deadlock scenario, TIBCO recommends to set the com.tibco.bx.lockWaitNotify=true property and the value of bw.engine.db.maxConnection property = twice the value of bw.engine.threadCount.

AMBW-42815 The performance is degraded in the Iterate group.
AMBW-42771 The Iterate group maps incorrect data to the iteration element when the Iterate group is executed by multiple jobs at the same time.
AMBW-41331 Two applications incorrectly refer to the same hashmap in some cases when an AppNode starts the applications at the same time, and an activator process is used along with custom XPath functions.

Release 2.6.1

Key Description
BWCE-3712 An exception occurs in debug mode for console, when the ASCII Characters are not be serialized or parsed in XML.
AMBW-42418 The BW.MODULE.NAME and BW.MODULE.VERSION module properties return empty values.
AMBW-42416

On stopping an application, the application cannot call the delete method of the shared resource when the shared resource uses a module property in one of the fields.

AMBW-42125

TIBCO Business Studio for BusinessWorks displays an error message for the OAuth Configuration shared resource when the confidentiality is not defined for the HTTPS.

AMBW-40159

Modifications done inside a running application in TIBCO Business Studio for BusinessWorks displays the Process not found error.

Release 2.6.0

Key Description
BWCE-3396 The JDBC Call Procedure activity failed by timeout when the store procedure used had a complex nested array type of objects.
BWCE-1665 The performance of xsl:apply-templates was poor, when the optional Select attribute contained a XPath expression which was not an empty string. The optimizer now recognizes such XPath expressions that can be sped up, and improves performance in supported cases significantly.
AMBW-41486 The <?xml-multiple?> tag disappeared from the output of the Parse XML activity when the Validate Output check box was selected.

Set the -Dbw.application.activity.validateOutput.treeValidation=true property as VM argument to add the tag when validating an output XML.

AMBW-41289 The <msgCode> tag under FaultDetails could not capture the actual msgCode value.
AMBW-41222 An application was unable to resolve a process variable on startup for the Assign activity, even though the Call Process activity in the same process could resolve the same process variable.
AMBW-41218 The Engine Command activity did not stop an application when an application was restarted.
AMBW-41207 Memory leak issue was observed due to an instance of to org.eclipse.xsd.XSDSchemaDirective[] on an AppNode.
AMBW-41045 After upgrading, the Transform XML activity took more memory and generated the Out of Memory Exception.
AMBW-40793 An application could not be started when its status was STARTFAILED.
AMBW-40362 An application using WSDL from a shared module failed to restart and displayed the java.lang.IllegalStateException: BundleContext is no longer valid error.
AMBW-40232 The conversation handler failed when multiple AppNodes were set up in a group persistence mode.
AMBW-40145 Ability to evaluate transition expression as XPath 1.0 expression

Set the bw.engine.use.transition.xpath.expression.lang.1.0 property to true in the AppNode's config.ini file.

By default, the value is false.

AMBW-38813 The performance was degraded in the Iterate Group activity.
AMBW-36149 When an application had a persistent shared module in the group mode, the following error occurred intermittently: PVM-MODEL-102700.
AMBW-33830 After migration, the Repeat group used in a calling process displayed java.sql.SQLException when the JDBC Query activity was configured with a process in subsets used inside a subprocess.