Core Runtime

The following issues have been fixed in this release of TIBCO ActiveMatrix BusinessWorks™.

Release 6.10.0

Key Summary
AMBW-48899 The startup time of the BusinessWorks application increases after using a larger schema.
AMBW-48714 When two SOAP applications are started on the same AppNode simultaneously, then one of them fails to start.
AMBW-48648 The application configured with the property bw.independent.component.startup=true goes into a stopping state when any of the shared resources are not available.
AMBW-48486 BusinessWorks application having "Activator" as the only component remains in the Stopping state.
AMBW-48484 The checkpoint-related data is deleted from the pg_largeobject table after enabling the bw.engine.enable.checkpointdata.delete property for the PostgreSQL database.
AMBW-47920 ActiveMatrix BusinessWorks 6.x application with heavy XSLT mapping takes more than 15 minutes to start.
AMBW-46361 An NPE error is thrown in AppNode logs for Group mode with the Oracle database.
AMBW-28658 The AppNode logs fail to log an error/reason for the impaired state of an application.

Release 6.9.1

Key Summary
AMBW-48181 The activator process is slow when running an activity with large XML data in Debug mode.
AMBW-43215 For the SAP application, If the SAP component is not available, then the application goes into an impaired/start failed state.

Release 6.9.0

Key Summary
AMBW-46544 Application deployed to AppSpace configured in FT-group mode and FTL as group provider activates more than one active instance on restarting FTL servers configured in FT mode.
AMBW-46534 When Appnodes are configured in FT-group, the wrong Component status is shown differently on TIBCO® Enterprise Administrator UI and via REST API calls.
AMBW-46530 SOAP/JMS service throws an error, "cache cannot be null.stacktrace : java.lang.AssertionError: cache cannot be null" when the JMS receiver configured to the queue has a lot of pending messages more than the relative flow limit set for the component.
AMBW-46514 Heap memory increases due to memory leaks while using Notify and ReceiveNotification activities.
AMBW-46502

At runtime in ftgroup mode with weighted property, when the application contains a service-based sub-process call in a process, the Fault Tolerance mechanism stops working post secondary fail-over.

A property named "bw.engine.ftgroup.activator.servicesubprocess" is now provided to fix this issue.
AMBW-46207 Applications with subprocess calls without the Spawn option are moving into an unresponsive state in group persistence appspaces because of logical deadlock.
AMBW-45361 The stopapp/startapp OSGi commands are not working in TIBCO ActiveMatrix BusinessWorks™ 6.7.x and 6.6.x code bases.
AMBW-39684 An "Attribute DataType cannot be null" error occurs when coercion is used for the "anyType" element in the iteration loop.
AMBW-36995 Variables inside the iterate loop do not reset after each iteration when they are not executed again.

Release 6.8.1

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

Release 6.8.0

Key Summary
AMBW-44452 When migrating the 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 reco..///very system.

Set the com.tibco.bx.engine.recovery.failure.threshold property to a value between 31 to 180 seconds.
 

TIBCO ActiveMatrix BusinessWorks SharedVariable does not reset to initial value after deployed application restart.

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

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 ActiveMatrix BusinessWorks 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 6.7.0

Key Summary
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.