Runtime Issues

  1. Monitoring Your BPM Node
    You can use either JConsole or JVisualVM to monitor your BPM node. These are standard Java tools. These tools are useful if you wish to specifically monitor the JVM Heap Memory usage, the CPU usage, the number of threads or to monitor the JVM in general.
  2. Creating a New BPM Node with TCT Causes Failures
    The BPM Server Node Type wizard fails at the last phase of the process (distributing the product application to the newly created node) if any of the child user applications that have been deployed to the product application are in a “Failed” state. Before adding a new node, rectify the issue with the broken user application so that it is no longer in a “Failed” state.
  3. Recovering From a BPM Node Crash
    Restarting the BPM node after a crash may sometimes fail and/or stop process work because of various reasons. This may be because some work items are missing or the BPM application changes to a ’Partially Running’ runtime state.
  4. Removing applications from a node
    After removing BPMNode from the amx.bpm.app distribution (and hence all user applications), all BDS Applications go to a 'Deploy with Start Failed' state.
  5. Rescheduling Process Instances Stuck in Starting State after a Node Crash
  6. Preventing Process Instances from Failing and being Purged if a System Error Occurs
    Unexpected system errors can result in the failure of process instances that would otherwise have continued to run - for example, if a database connection failure occurs during an update, or a system memory error occurs while a script is running.
  7. Suspended Timer Event Behavior
    When a process instance with a timer event configured is suspended, the timer event continues to be processed. However, you will not see any effect until the process instance resumes.
  8. Troubleshooting BPM Node has a Status of Out of Sync
    In TIBCO Administrator, the BPM node is displayed as "Out of Sync". This indicates that the BPM node is not running the latest configuration. This means inconsistent results may be achieved when performing an upgrade or when reprovisioning the node, for example.
  9. Missing Application Dependencies
    You can have missing application dependencies when user applications have outstanding process instances when upgrading or when upgrading a sub-process application when a version of the parent process application is preparing to undeploy.
  10. Reallocate Work Item is Failing
    Work items allocated using RQL do not appear in any managed work lists as they are not directly associated with specific organizational entities. You should use dynamic performer fields to get the association of work items to organizational entities functionality.
  11. Maximum Number of Tasks Allowed Has Been Reached
    It is possible for a runaway process to generate a very large number of tasks within a single instance, resulting in a large number of EC events for the instance, as well as a large number of rows in the PVM database tables for the instance.
  12. "Could not commit with auto-commit set on" SQLException From Oracle 12c JDBC Driver
    A "Caused by: java.sql.SQLException: Could not commit with auto-commit set on" SQLException is reported in the BPM node log file.
  13. A Business Service Fails to Start
    A business service fails to start. The service exception WPEXT_START_BUSINESS_SERVICE_FAULT is displayed.
  14. Process Halts with "... cannot be cast to..." Error
    This topic describes what to do if you have a process that halts with the following error: ApplicationName.bdsutil.BDSNotifyingCalendar cannot be cast to com.sun.org.apache.xerces.internal.jaxp.datatype.XMLGregorianCalendarImpl