JR44634: RUNTIMEEXCEPTION, WITH THE FOLLOWING MESSAGE "DISPOSE() CALLED BUT RUNNER ON TOP OF STACK NOT THIS RUNNER."

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

APAR status

• Closed as program error.

Error description

• When resuming a BPD instance from within JavaScript in a
  specific order you may get the following error -
  [23/10/12 13:29:57:944 CEST] 000001fc wle           E
  CWLLG0594E: An
  exception occurred while initializing the runnable thread.
  Error:
  java.lang.RuntimeException: dispose() called but runner on top
  of stack
  not this runner.  Need to enable trace to get runner creation
  location.
    java.lang.RuntimeException: dispose() called but runner on
  top of
  stack not this runner.  Need to enable trace to get runner
  creation
  location.
  

Local fix

• N/A
  

Problem summary

• Problem Description:
  
  RuntimeException: "JavaScriptRunner.dispose() was invoked with a
  a runner that
  was not at the top of the stack." when calling the JavaScript
  API resumeInstance
  from within nested JavaScript calls.
  
  The stack trace will look like this:
  
  CWLLG0434E: JavaScriptRunner.dispose() was invoked with a a
  runner that was not at the top of the stack.  The top of stack
  runner was created by java.lang.Throwable
   at
  com.lombardisoftware.core.script.js.JavaScriptRunner.<init>(Java
  ScriptRunner.java:133)
   at
  com.lombardisoftware.bpd.runtime.engine.BPDExecutionContext.getJ
  SScriptRunner(BPDExecutionContext.java:265)
   at
  com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.get
  JSScriptRunner(BPDExecutionTreeNode.java:534)
   at
  com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.eva
  luateExpression(BPDExecutionTreeNode.java:638)
   at
  com.lombardisoftware.bpd.runtime.engine.BPDExecutionTreeNode.eva
  luateExpression(BPDExecutionTreeNode.java:608)
   at
  com.lombardisoftware.bpd.runtime.engine.AbstractWorkerContext.ev
  aluateExpression(AbstractWorkerContext.java:42)
   at
  com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti
  merEventWorkerHelper.calculateIncrementAmount(TimerEventWorkerHe
  lper.java:501)
   at
  com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti
  merEventWorkerHelper.calculateRelativeToDueDate(TimerEventWorker
  Helper.java:310)
   at
  com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ti
  merEventWorkerHelper.calculateTargetTime(TimerEventWorkerHelper.
  java:259)
   at
  com.lombardisoftware.bpd.component.flowcomponent.event.worker.Ev
  entWorker.calculateTimerTargetTime(EventWorker.java:266)
   at
  com.lombardisoftware.bpd.runtime.engine.quartz.BPDSchedulerHelpe
  r.resumeRunningTimer(BPDSchedulerHelper.java:293)
   at
  com.lombardisoftware.server.ejb.bpd.BPDEngineServicesCore.resume
  Instance(BPDEngineServicesCore.java:1040)
  
  Problem Summary:
  
  When the cleanup mechanism tries remove the context used to
  execute JavaScript,
  the cleanup fails, because the current context does not belong
  to the function
  that needs to be cleaned up.
  
  Problem Conclusion:
  
  The fix ensures, that the cleanup takes place when the
  JavaScript was executed
  and the context can be disposed.
  

Problem conclusion

• Problem will be fixed with V8001
  

Temporary fix

Comments

APAR Information

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

  JR44633

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

Fix information

• Fixed component name

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R800 PSY

     UP