JR46270: DEPLOYMENT OF BPM PROCESS APPLICATION HANGS WHEN CUSTOM DEPLOYMENT SERVICE MAKES TWO DB CALLS ON SAME SNAPSHOT.

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

APAR status

• Closed as program error.

Error description

• When attempting to install a Process application on Process
  server from Process Designer or Process Console admin, the
  install takes forever and hangs.
  
  This happens because custom deployment service is making two
  database calls on same snapshot.
  
  e.g: Following sample code causes hung thread during deployment
  
  var twProcessApp = tw.system.model.processApp;
  var tmpSnapshot = twProcessApp.defaultSnapshot;
  twProcessApp.defaultSnapshot = twProcessApp.currentSnapshot;
  if (tmpSnapshot) {
     tmpSnapshot.deactivate();
  }
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  BPM 751 users using the default deployment  *
  *                  service.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: The java script implementation within   *
  *                      the deployment service makes two API    *
  *                      calls on the same snapshot. One is to   *
  *                      make hte snapshot non-default and the   *
  *                      other transaction is to deactivate      *
  *                      it. This causes a hung thread as        *
  *                      these two calls are running in two      *
  *                      different transaction scopes.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem is isolated to a case where the users implementing
  the default deployment service make two db calls on the same
  snapshot. This could result in hung threads when two API calls
  operating on the same snapshot.
  

Problem conclusion

• The fix is given to ensure that all the db transactions from
  the deployment service call run in an existing transaction.
  
  Install/Dependency information is available in the readme.txt
  on FixCentral. When the user goes to the download files page
  in FixCentral, the readme will be available with the fix
  package as a separate download.
  

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

• Fixed component name

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R750 PSY

     UP