JR51032: OUTOFMEMORYERROR WITH CLASS SYMBOLTABLENAMESPACEIMPL

8.0.1.2-WS-BPM-IFJR51032
8.5.0.1-WS-BPM-IFJR51032
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 observe OutOfMemoryErrormessages or growing memory
  consumption with regard to class
  com.lombardisoftware.server.core.SymbolTableNamespaceImpl.
  This could happen if you have a huge number of sub-processes as
  part of your BPDs.
  
  When you run a heapanalyzer tool on current heapdumps you can
  see that a huge amount of memory is consumed by
  ConcurrentHashMaps in the context of
  com.lombardisoftware.component.common.workflow.ExecutionContext.
  Here is an excerpt of such an heapanalyzer output:
  
  class
  com.lombardisoftware.component.coachng.gen.CoachGeneratorContext
  Manager 80  1,221,942,064 37.62%
  java.util.concurrent.ConcurrentHashMap       48  1,221,941,976
  37.62%
  java.util.concurrent.ConcurrentHashMap$Segment[16]     80
  1,221,941,928 37.62%
  java.util.concurrent.ConcurrentHashMap$Segment       32
  286,588,040   8.82%
  java.util.concurrent.ConcurrentHashMap$Segment       32
  189,753,952   5.84%
  com.lombardisoftware.component.common.workflow.ExecutionContext
     200 164,614,880   5.07%
  java.util.concurrent.ConcurrentHashMap$Segment      32
  122,241,560    3.76%
  java.util.concurrent.ConcurrentHashMap$Segment       32
  90,229,728   2.78%
  java.util.concurrent.ConcurrentHashMap$Segment       32
  77,151,896   2.38%
  java.util.concurrent.ConcurrentHashMap$Segment       32
  67,708,080   2.08%
  java.util.concurrent.ConcurrentHashMap$Segment       32
  53,038,184   1.63%
  com.lombardisoftware.component.common.workflow.ExecutionContext
     200 32,221,920   0.99%
  com.lombardisoftware.component.common.workflow.ExecutionContext
     200 28,600,312   0.88%
  java.util.concurrent.ConcurrentHashMap$Segment      32
  27,250,344   0.84%
  com.lombardisoftware.component.common.workflow.ExecutionContext
     200 20,944,832  0.64%
  java.util.concurrent.ConcurrentHashMap$Segment       32
  16,597,040  0.51%
  com.lombardisoftware.component.common.workflow.ExecutionContext
     200 12,428,256  0.38%
  com.lombardisoftware.component.common.workflow.ExecutionContext
    200 9,806,368  0.30%
  java.util.concurrent.ConcurrentHashMap$Segment       32
  7,457,976  0.23%
  java.util.concurrent.ConcurrentHashMap$Segment       32
  3,952,040  0.12%
  java.util.concurrent.ConcurrentHashMap$Segment      32
  2,865,528  0.09%
  java.util.concurrent.ConcurrentHashMap$Segment      32
  2,150,704  0.07%
  
  
  And in each ConcurrentHashMap or ExecutionContext, you can find
  the deep object stack, as the following:
  
  |-> com.lombardisoftware.server.core.SymbolTable
    |-> java.util.ArrayList
      |-> array of Java.lang.Object
        |->
  com.lombardisoftware.server.core.SymbolTableNamespaceImpl
  

Local fix

Problem summary

• When a  sub-process is started, the BPD engine ensures that all
  variables of the sub-process can be deserialized from the
  XML-representation and runs some initialization logic. This
  logic uses a list of variable scopes. The handling of the list
  is incorrect and the list can grow all the time.
  

Problem conclusion

• A fix is/will be available that removes the incorrect list
  handling.
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR51032:
  
  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 JR51032, 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

• R850 PSY

     UP

• R855 PSY

     UP