Runtime

This topic lists the Closed Issues related to Runtime.

Release 2.10.0

Key Summary
BWCE-4307

When memory saving mode is enabled, some shared variable values is getting cleared.

AMBW-50954 A "java.util.ConcurrentModificationException" error occurs in the AppNode configuration logs. This has been fixed now.
AMBW-50437 The G1 Old Gen memory keeps increasing until it consumes all the heap memory.
AMBW-46596 When a pipe ("|") character is used in XSD, it does not throw any design time validation error but throws a schema loading-related error at runtime.
AMBW-38591 After the refresh interval of the keystore, the module property is not picked up at runtime.
BWCE-7583 While compiling XPath methods, the processing time is more in each TIBCO BusinessWorks process worker threads.

The following are the system properties used to reduce the time consumption while compiling XPath methods:

  • bw.xml.xpath.cacheExpressions - true/false

  • bw.xml.xpath.cacheExpressions.size - The default value of 2750. This value is arbitrary.

  • bw.xml.xpath.cacheExpressions.percent - The default value is 8. The percentage of the cache purged if full.

Release 2.9.2

Key Summary
AMBW-50586

In the "Repeat on Error" loop, activities, if faulted, remain in the Starting state even after completion.

Now they are displayed in the Completed state.

AMBW-50559 The G1 Old Gen memory keeps increasing until it consumes all the heap memory.
AMBW-50471 Properties used to skip validation, particularly for parseXML activity are not working in GROUP mode.

Release 2.9.1

Key Summary
BWCE-6862 The Job View displays wrong information on the Job Shared Variables in Spawned process if the activity name is same.
BWCE-6781 While configuring circuit breaker with the HTTP Client shared resource the 422 status error code exceptions are not ignored.
BWCE-6669 In BWCE 2.9.1, due to EOL com.tibco.tpcl.com.ibm.icu_3.9.0.001/'icu4j-3_8_1.jar is upgraded to com.tibco.tpcl.com.ibm.icu_3.9.200.002/icu4j-74.1.jar version to resolve the icu4j EOL .
BWCE-5902

While compiling XPath methods, the processing time is more in each TIBCO BusinessWorks process worker threads.

The following are the system properties used to reduce the time consumption while compiling XPath methods:

  • bw.xml.xpath.cacheExpressions - true/false

  • bw.xml.xpath.cacheExpressions.size - The default value of 2750. This value is arbitrary.

  • bw.xml.xpath.cacheExpressions.percent - The default value is 8. The percentage of the cache purged if full.

BWCE-5635 Properties from environment variables does not throw error even if those properties are not using configuration management services.
AMBW-49572 Application-related logs are getting printed on both Application as well as AppNode log files leading to duplicate logs.

Release 2.9.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 2.8.3

Key Summary
AMBW-47873 When two SOAP applications are started on the same AppNode simultaneously, then one of them fails to start.

Release 2.8.2

Key Summary
BWCE-5410 The TIBCOJRE is hardcoded in the setup.sh file.
BWCE-5391 The Configuration Management Services for AWS is not working if the application name is not set.
BWCE-5374 The format of number fields gets changed when they are of type string fields.
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 2.8.1

Key Summary
AMBW-47598 Running an application with an activator process and large XML throws an out-of-memory error in Debug mode.
AMBW-47549 Input mapped from SalesforceQueryAll shows trimmed output in Mapper output activity. For example, the decimal value of "1200.0" is trimmed to "1200".
AMBW-46825

The white space characters in the appspace configuration.ini files fail to start in the appnode/application.

The BWEngine now smartly removes the spaces, tabs, and other special characters while retrieving the configuration values from configuration files.

Release 2.8.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 2.7.3

Key Summary
AMBW-46512 Heap memory increases due to memory leaks while using Notify and ReceiveNotification activity
AMBW-46104 Applications with subprocess calls without the Spawn option are moving into an unresponsive state in group persistence appspaces because of logical deadlock.
AMBW-45599 At runtime in ftgroup mode with weighted property, when the application contains a service based subprocess call in a process, the Fault Tolerance mechanism stops working post secondary fail-over.

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.