JR53757: MULTIPLE JAVASCRIPTRUNNER EXCEPTIONS FLOOD SYSTEMOUT.LOG FILE

8.5.0.1-WS-BPM-IFJR53757
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5 Refresh Pack 7 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• In a system under load, millions of JavaScriptRunner exceptions
  are produced within a few minutes, making the SystemOut.log file
  unusable.
  
  If you set trace criteria to WLE.wle=finest or WLE.*all, you see
  SystemOut.log entries like the following entries:
  ﾎ29/06/15 18:39:04:562ﾚ 000064f2 wle            X   CWLLG0399W:
  JavaScriptRunner(...) nesting depth > 10 depth=23
  ﾎ29/06/15 18:39:04:563ﾚ 000064f2 wle            X   CWLLG0400W:
  Frame ''0'' was created by java.lang.Throwable
    JavaScriptRunner$JavaScriptRunnerFrame.<init>
    (JavaScriptRunner.java:603)
   at com.lombardisoftware.core.script.js.JavaScriptRunner.
    <init>(JavaScriptRunner.java:144)
   at com.lombardisoftware.bpd.runtime.engine.
    BPDExecutionContext.getJSScriptRunner(BPDExecutionContext.
    java:360)
   at com.lombardisoftware.bpd.runtime.engine.
    BPDExecutionTreeNode.getJSScriptRunner(BPDExecutionTreeNode.
    java:581)
   at com.lombardisoftware.bpd.runtime.engine.
    BPDExecutionTreeNode.evaluateExpression(BPDExecutionTreeNode.
    java:685)
   at com.lombardisoftware.bpd.runtime.engine.
    BPDExecutionTreeNode.evaluateExpression
    (BPDExecutionTreeNode.java:655)
   at com.ibm.bpm.rest.jaxb.mapping.BPDMappingUtils$1.
    doExecuteDuringLock(BPDMappingUtils.java:616)
   at com.lombardisoftware.bpd.runtime.engine.util.
    LockBPDInstanceCommand$1.doInTransaction
    (LockBPDInstanceCommand.java:62)
   at com.lombardisoftware.server.core.TXCommand$2.
    call(TXCommand.java:85)
   at com.lombardisoftware.utility.spring.
    ProgrammaticTransactionSupport$1.doInTransaction
    (ProgrammaticTransactionSupport.java:436)
   at org.springframework.transaction.jta.
    WebSphereUowTransactionManager$UOWActionAdapter.run
    (WebSphereUowTransactionManager.java:306)
   at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.
    runUnderNewUOW(EmbeddableUOWManagerImpl.java:791)
   at com.ibm.ws.uow.embeddable.EmbeddableUOWManagerImpl.
    runUnderUOW(EmbeddableUOWManagerImpl.java:370)
   at org.springframework.transaction.jta.
    WebSphereUowTransactionManager.execute
    (WebSphereUowTransactionManager.java:252)
   at com.lombardisoftware.utility.spring.
    ProgrammaticTransactionSupport.executeInNewTransaction
    (ProgrammaticTransactionSupport.java:431)
   at com.lombardisoftware.utility.spring.
    ProgrammaticTransactionSupport.execute
    (ProgrammaticTransactionSupport.java:294)
   at com.lombardisoftware.server.core.TXCommand.
    executeInDeadlockRetryLoop(TXCommand.java:83)
   at com.lombardisoftware.bpd.runtime.engine.util.
    LockBPDInstanceCommand.execute
    (LockBPDInstanceCommand.java:74)
   at com.ibm.bpm.rest.jaxb.mapping.BPDMappingUtils.
    gatherVariablesForExecutionTreeNode(BPDMappingUtils.java:625)
   at com.ibm.bpm.rest.jaxb.mapping.BPDMappingUtils.
    scrapeVariablesForExecutionTreeNode(BPDMappingUtils.java:561)
   at com.ibm.bpm.rest.jaxb.mapping.BPDMappingUtils.
    getExecutionTree(BPDMappingUtils.java:488)
   at com.ibm.bpm.rest.jaxb.mapping.BPDMappingUtils.
    describeBPDInstance(BPDMappingUtils.java:425)
   at com.ibm.bpm.rest.jaxb.mapping.BPDMappingUtils.
    describeBPDInstance(BPDMappingUtils.java:183)
   at com.ibm.bpm.rest.impl.process.StartActionHandler.
    handleAction(StartActionHandler.java:169)
  

Local fix

Problem summary

• If you set trace criteria to WLE.wle=finest or WLE.*all,
  millions of JavaScriptRunner exceptions are written to the
  SystemOut.log file within a very short time because the
  JavaScriptRunner frame is not disposed of when it is no longer
  needed.
  

Problem conclusion

• A fix is planned to be made available for IBM BPM that disposes
  of the JavaScriptRunner frame when it is no longer needed.
  
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR53757:
  
  1. Select IBM Business Process Manager with your edition from
    the product selector, the installed version to the fix pack
    level, and your platform, and then click Continue.
  
  2. Select APAR or SPR, enter JR53757, and click Continue.
  
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

Temporary fix

• Not applicable
  

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

• R850 PSY

     UP

• R855 PSY

     UP

• R856 PSY

     UP