JR56707: YOU RECEIVE A NULLPOINTEREXCEPTION WHEN RUNNING A PROCESS WITH AUSER TASK THAT IS A LOOP AND HAS A TIMER BOUNDARY EVENT

bpm.8570.cf2016.12.delta.repository
Downloading IBM Business Process Manager V8.5.7 Cumulative Fix 2016.12

APAR status

• Closed as program error.

Error description

• If you run a process with a user task that is defined to run as
  a multi-instance or simple loop, and this task has a timer
  boundary event with a trigger specified relative to the task's
  due date, the process fails with an exception similar to the
  following exception, which you see in the SystemOut.log file of
  the server:
  
  [8/30/16 15:17:11:482 BRT] 00000158 wle           E
  CWLLG0326E: A deliverException has occurred.
                                   java.lang.NullPointerException
  at
  com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti
  merEventWorkerHelper.getSentTaskId(TimerEventWorkerHelper.java:4
  33)
  at
  com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti
  merEventWorkerHelper.calculateRelativeToDueDate(TimerEventWorker
  Helper.java:410)
  at
  com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti
  merEventWorkerHelper.calculateTargetTime(TimerEventWorkerHelper.
  java:352)
  at
  com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti
  merEventWorkerHelper.processIntermediateAction(TimerEventWorkerH
  elper.java:130)
  at
  com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ev
  entWorker.doWork(EventWorker.java:144)
  at
  com.lombardisoftware.bpd.runtime.engine.FlowObjectExecutionTreeN
  ode.doWork(FlowObjectExecutionTreeNode.java:373)
  at
  com.lombardisoftware.bpd.runtime.engine.FlowObjectExecutionTreeN
  ode.executeAttachedEvents(FlowObjectExecutionTreeNode.java:633)
  at
  com.lombardisoftware.bpd.runtime.engine.FlowObjectExecutionTreeN
  ode.doWork(FlowObjectExecutionTreeNode.java:380)
  at
  com.lombardisoftware.bpd.runtime.engine.BPDEngine.executeTreeNod
  e(BPDEngine.java:337)
  at
  com.lombardisoftware.bpd.runtime.engine.BPDEngine.resume(BPDEngi
  ne.java:180)
  ...
  

Local fix

• Change the process model and define the timer boundary event in
  a different way. There are several options other than relative
  to due date, for example, you could define the timer boundary
  event relative to the start of the step or a custom date that is
  hardcoded or is from a process variable.
  

Problem summary

• If a user task runs in a loop, each task instance has its own
  due date. A timer boundary event on an activity is a timer for
  the overall activity, not a timer for each instance of the loop.
  There is only one timer and that one timer cannot be calculated
  relative to multiple different due dates of several task
  instances. It is, therefore, not possible to run a process in
  such a combination.
  

Problem conclusion

• A fix will be included in IBM BPM V8.5.7 cumulative fix 2016.12
  that shows a validation error for processes that contain such a
  non-executable definition. If a user still models and runs this
  task, an improved failure message is provided.
  
  To determine whether the IBM BPM V8.5.7 cumulative fix 2016.12
  is available and download it if it is, complete the following
  steps on Fix Central:
  
  1. On the Select product tab, select WebSphere as the product
  group, IBM Business Process Manager with your edition from the
  WebSphere options, All as the installed version, and All as the
  platform, and then click Continue.
  2. In the Text field, enter "cumulative fix", and click
  Continue.
  
  PRODUCTS AFFECTED
  IBM Business Process Manager (BPM) Advanced
  IBM BPM Standard
  IBM BPM Express
  

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

• R857 PSY

     UP