JR49331: BPD PROCESS INSTANCE NAVIGATION STOPS AFTER LDAP EXCEPTION.

Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products
Download Version 8.0.1 Fix Pack 3 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• The problem being fixed with this APAR happened in the following
  scenario: There is a BPD instance that attempts to resolve a
  user by its
  name in a Java Script node, using the Java Script function:
  tw.system.org.findUserByName().
  At the point in time when this function was called, the LDAP
  System was
  not available. The call to the user registry reported an
  exception but
  this exception was swallowed. As a side effect of the LDAP
  exception the
  current transaction was marked for rollback only, but since the
  exception never reached the BPD engine, it assumes that the
  execution of
  the task was successful. The process instance actually stopped
  at the
  precedent task.
  This fix improves the transactional behavior of the BPD engine.
  

Local fix

• n/a
  

Problem summary

• The problem being fixed happened in the following scenario:
  There is a BPD instance that attempts to resolve a user by its
  name in a Java Script node, using the Java Script function:
    tw.system.org.findUserByName().
  
  At the point in time when this function was called, the LDAP
  server was not available. So the call to the user registry
  reported an exception. The exception is caught and the
  navigation proceeds, assuming that the user does not exist.
  But, unfortunately, the current transaction is marked for
  rollback only.
  But since the exception never reached the BPD engine, it assumes
  that the execution of the task was successful. As a result the
  process instance actually stopped at the precedent task.
  

Problem conclusion

• This fix improves the transactional behavior of the BPD engine
  in two ways:
  (1) User registry calls are moved into a new transaction. Thus
  an exception thrown from the User registry can no longer
  influence the BPD navigation transaction.
  (2) The transactional behavior of the BPD engine is improved in
  general, so that it detects when a navigation transaction is
  marked for rollback-only also in a situation where no exception
  is reported to the engine.
  
  FIX AVAILABILITY:
  iFix for 8.0.1.0 is/will be available on Fix Central; search for
  APAR JR49331 at http://www.ibm.com/support/fixcentral/
  Fix is also targetted for inclusion in next fixpack for
  BPM V8.0.1
  
  When obtaining any of the above fixes, be sure to download the
  accompanying readme, for itself, and any prerequisite fixes, and
  review them thoroughly.
  

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 STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R801 PSY

     UP