JR47885: TRANSACTIONALITY OF BPD NAVIGATION AND EVENT EMISSION FOR MONITORING COULD LEAD TO TRANSACTION ROLLBACKS

Download Version 8.0.1 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 1 for the IBM Business Process Manager products

APAR status

• Closed as fixed if next.

Error description

• Business process definition (BPD) navigation and event
  emission to a JMS queue for monitoring via the Business
  Monitor product are included in the same transaction.  This
  ensures that monitoring data accurately reflects the state of
  the business process.
  
  If the Business Monitor system is not available or the JMS
  queue for event delivery becomes full, then it will no longer
  be possible to emit events to the JMS queue.  Then Business
  Process Manager transactions for the business process will
  fail and roll back so that process and monitoring data remain
  synchronized.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of BPM Express, BPM Standard, and     *
  *                  BPM Advanced.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: The Business Process Manager product    *
  *                      worked as designed so that process      *
  *                      and monitoring data would remain        *
  *                      synchronized.  However, if a customer   *
  *                      is more interested in process           *
  *                      completion that monitoring data         *
  *                      accuracy, then the fact that BPD        *
  *                      navigation and event emission are       *
  *                      included in the same transaction        *
  *                      could restrict process completion if    *
  *                      the JMS queue for event delivery is     *
  *                      full.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Changes have been made in Business Process Manager to
  introduce a configuration option that will separate BPD
  navigation and event emission for monitoring into different
  transactions.  As a result, if the JMS queue for event
  delivery is full, the BPD navigation will continue and
  processes can complete.
  Please note that enabling this configuration option has the
  potential to decrease accuracy of monitoring data provided to
  the Business Monitor product.
  -If a process continues, but monitoring data is not emitted,
  then there will not be monitoring data for part of the process.
  -If monitoring data is emitted, but a process rolls back, then
  there could be an attempt to emit monitoring data multiple
  times for the same process instance.
  Following are instructions for setting the configuration
  option to separate BPD navigation and event emission into
  different transactions.  Add the following JVM property to the
  stand-alone server or every member of the Application cluster
  for a network deployment environment.
  1.  Start only the deployment manager for a network deployment
  environment or the stand-alone server for a stand-alone
  environment.
  2.  Launch the WebSphere administrative console.
  3.  Select an application server by navigating to Servers >
  Server Types > WebSphere application servers > <server name>.
  4.  Then under the Server Infrastructure section, navigate to
  Java and process management > Process definition > Java
  virtual machine > Custom properties.
  5.  Add the following property:
  com.lombardisoftware.server.monitor.MonitorEventEmitter.qos.tran
  saction.new
  6.  Set the value of the new property as: true
  7.  Repeat steps 3-6 for additional Application cluster
  members in a network deployment environment.
  8.  Start the remainder of the network deployment environment
  or restart the stand-alone server.
  Note that changes for JR47885 are included in Business Process
  Manager 8.0.1 Fix Pack 2 (8.0.1.2).
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R800 PSY

     UP