JR51774: IBM BPM PROCESS SERVER USES A LOT OF CPU WHEN RUNNING JAVASCRIPT

8.5.5.0-WS-BPM-IFJR51774
8.0.1.3-WS-BPM-IFJR51774
8.5.0.1-WS-BPM-IFJR51774
8.0.1.2-WS-BPM-IFJR51774
Version 8.5 Refresh Pack 6 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• You notice that running an IBM Business Process Manager (BPM)
  process uses a lot of CPU and sometimes the system hangs. In a
  Java core dump, the Java callstack might look similar to the
  following callstack:
  
  at java/util/HashMap.findNonNullKeyEntry(HashMap.
    java:601(CompiledCode))
  at java/util/HashMap.getEntry(HashMap.java:585(CompiledCode))
  at java/util/HashMap.get(HashMap.java:571(Compiled Code))
  at org/mozilla/javascript/JavaMembers.lookupClass
    (JavaMembers.java:833(Compiled Code))
  at org/mozilla/javascript/NativeJavaObject.initMembers
    (NativeJavaObject.java:90(Compiled Code))
  at org/mozilla/javascript/NativeJavaObject.<init>
    (NativeJavaObject.java:80(Compiled Code))
  at org/mozilla/javascript/NativeJavaObject.<init>
    (NativeJavaObject.java:70(Compiled Code))
  at org/mozilla/javascript/WrapFactory.wrapAsJavaObject
    (WrapFactory.java:149(Compiled Code))
  at org/mozilla/javascript/WrapFactory.wrap(WrapFactory.
    java:105(Compiled Code))
  at org/mozilla/javascript/NativeJavaMethod.call
    (NativeJavaMethod.java:258(Compiled Code))
  at org/mozilla/javascript/Interpreter.interpretLoop
    (Interpreter.java:3330(Compiled Code))
  at org/mozilla/javascript/Interpreter.interpret
    (Interpreter.java:2487(Compiled Code))
  at org/mozilla/javascript/InterpretedFunction.call
    (InterpretedFunction.java:164(Compiled Code))
  at org/mozilla/javascript/ContextFactory.doTopCall
    (ContextFactory.java:398(Compiled Code))
  at org/mozilla/javascript/ScriptRuntime.doTopCall
    (ScriptRuntime.java:3070(Compiled Code))
  at org/mozilla/javascript/InterpretedFunction.exec
    (InterpretedFunction.java:175(Compiled Code))
  at com/lombardisoftware/core/script/js/JSScript.exec
    (JSScript.java:60(Compiled Code))
  
  .----------------------------------------------------
     Another possible symptom are hung threads (WSVR0605W) with
  the following java stack.
  .
  [10/22/14 16:05:42:467 EDT] 0000008e ThreadMonitor W
  WSVR0605W: Thread
   "WorkManager.bpm-em-workmanager : 14143" (00008332) has been
  active for
   668295 milliseconds and may be hung.  There is/are 2 thread(s)
  in total
   in the server that may be hung.
   at
  org.mozilla.javascript.NativeJavaPackage.getPkgProperty(NativeJa
  vaPackage.java)
   at
  org.mozilla.javascript.NativeJavaPackage.get(NativeJavaPackage.j
  ava:114)
   at
  org.mozilla.javascript.ScriptableObject.getProperty(ScriptableOb
  ject.java:1617)
   at
  org.mozilla.javascript.ScriptRuntime.getObjectProp(ScriptRuntime
  .java:1437)
   at
  org.mozilla.javascript.ScriptRuntime.getObjectProp(ScriptRuntime
  .java:1423)
   at
  org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.jav
  a:3027)
   at
  org.mozilla.javascript.Interpreter.interpret(Interpreter.java:24
  87)
   at
  org.mozilla.javascript.InterpretedFunction.call(InterpretedFunct
  ion.java:164)
  
  
  or this java stack
  
  [10/22/14 16:05:42:466 EDT] 0000008e ThreadMonitor W
  WSVR0605W: Thread
  "WorkManager.bpm-em-workmanager : 14148" (00008338) has been
  active for
  668295 milliseconds and may be hung.  There is/are 1 thread(s)
  in total
  in the server that may be hung.
      at java.util.HashMap.findNonNullKeyEntry(HashMap.java:601)
      at java.util.HashMap.getEntry(HashMap.java:585)
      at java.util.HashMap.get(HashMap.java:571)
      at
  org.mozilla.javascript.JavaMembers.lookupClass(JavaMembers.java:
  833)
      at
  org.mozilla.javascript.NativeJavaClass.initMembers(NativeJavaCla
  ss.java:84)
      at
  org.mozilla.javascript.NativeJavaClass.<init>(NativeJavaClass.ja
  va:78)
      at
  org.mozilla.javascript.NativeJavaPackage.getPkgProperty(NativeJa
  vaPackag
  e.java:164)
      at
  org.mozilla.javascript.NativeJavaPackage.get(NativeJavaPackage.j
  ava:114)
      at
  org.mozilla.javascript.ScriptableObject.getProperty(ScriptableOb
  ject.java:1617)
      at
  org.mozilla.javascript.ScriptRuntime.getObjectProp(ScriptRuntime
  .java:1437)
      at
  org.mozilla.javascript.ScriptRuntime.getObjectProp(ScriptRuntime
  .java:1423)
      at
  org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.jav
  a:3027)
      at
  org.mozilla.javascript.Interpreter.interpret(Interpreter.java:24
  87)
      at
  org.mozilla.javascript.InterpretedFunction.call(InterpretedFunct
  ion.java:164)
  

Local fix

Problem summary

• This issue occurs because the Rhino JavaScript engine uses an
  implementation that is not thread safe, which is fixed with
  Rhino 1.7R3. This Rhino fix is now included in the Rhino
  implementation that IBM BPM uses. For more information, visit
  Rhino Github and search for the bug fix number 738388.
  

Problem conclusion

• A fix is/will be available for IBM BPM  that contains the
  changes that were implemented with the official Rhino fix (bug
  fix number 738388).
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR51774:
  
  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 JR51774, 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

• R801 PSY

     UP