IV26266: RUNTIME EXCEPTION THROWN FROM A CUSTOM APIEVENTHANDLER DOES NOT STOP THE HUMAN TASK ACTIVITY

Version 8.0.1 Fix Pack 1 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

• Runtime exception thrown from a custom APIEventHandler does not
  stop the human task activity.
  .
  Consider a case where a custom APIEventHandler throws an runtime
  exception for the inline task of a human task activity in the
  start or create call. The expected behavior is, that the runtime
  exception leadsto an rollback of the current transaction. When
  the transaction is retried the fault handling logic is expected
  to be started -- e.g. fault handler is started or activity is
  put into stop state -- without creating or starting the task
  again. The problem is that the activity and its associated task
  is retried multiple times until a hold queue message is created.
  

Local fix

Problem summary

• Problem Description:
  Consider a case where a custom APIEventHandler throws an runtime
  exception for the inline task of a
  human task activity in the start or create call. The expected
  behavior is, that the runtime exception
  leads to a rollback of the current transaction. When the
  transaction is retried the fault handling logic
  is expected to be started -- e.g. fault handler is started or
  activity is put into stop state -- without
  creating or starting the task again. The problem is that the
  activity and its associated task is retried
  multiple times until a hold queue message is created.
  
  Problem Summary:
  There is a contract between Human Task Manager and BPEL Engine
  that rules in which cases the BPEL Engine
  should retry multiple times (recoverable exception) or retry
  only once (unrecoverable exception). This
  contract is implemented by the transactional context. The
  problem is caused because Human Task Manager
  and BPEL Engine use different transactional context instances.
  
  Problem Conclusion:
  The fix ensures that Human Task Manager and BPEL Engine are
  using the same transactional context instance.
  

Problem conclusion

• Problem fixed
  iFix available on top of V700 FP5
  

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:

  JR44875 JR44877 JR44878 JR44879

Fix information

• Fixed component name

  BUS PRC CHOREOG

• Fixed component ID

  5655FLW11

Applicable component levels