IBM Support

JR49413: PROCESS PORTAL TIMES OUT WHEN YOU GO TO PROCESS INSTANCE, HIGH CPU USAGE OCCURS DUE TO GC PROCESSING, and OUTOFMEMORYERRORs.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For some complex business process definitions (BPDs) that do not
    have distinguishable paths from the start to end nodes, the
    projected path cannot be calculated. In these cases, when you go
    to the Process Instance view, IBM Process Portal times out and
    the server indicates high CPU usage when you hover over the
    instance in the Process Performance dashboard.
    .
       One might see WSVR0605W messages with this java stack
    [2/7/14 12:14:03:098 CST] 000000a5 ThreadMonitor W   WSVR0605W:
    Thread
    "WebContainer : 0" (00000131) has been active for 720736
    milliseconds
    and may be hung.  There is/are 7 thread(s) in total in the
    server that
    may be hung.
        at java.lang.String.hashCode(String.java:742)
        at java.util.HashMap.hash(HashMap.java:132)
        at java.util.HashMap.getEntry(HashMap.java:583)
        at java.util.HashMap.containsKey(HashMap.java:506)
        at
    com.lombardisoftware.bpd.criticalpath.CriticalPath.processOutFlo
    w(CriticalPath.java:2186)
        at
    com.lombardisoftware.bpd.criticalpath.CriticalPath.dfs(CriticalP
    ath.java:1867)
        at
    com.lombardisoftware.bpd.criticalpath.CriticalPath.processOutFlo
    w(CriticalPath.java:2198)
        at
    com.lombardisoftware.bpd.criticalpath.CriticalPath.dfs(CriticalP
    ath.java:1928)
        at
    com.lombardisoftware.bpd.criticalpath.CriticalPath.processOutFlo
    w(CriticalPath.java:2198)
        at
    com.lombardisoftware.bpd.criticalpath.CriticalPath.dfs(CriticalP
    ath.java:1867)
        at
    com.lombardisoftware.bpd.criticalpath.CriticalPath.processOutFlo
    w(CriticalPath.java:2198)
        at
    com.lombardisoftware.bpd.criticalpath.CriticalPath.dfs(CriticalP
    ath.java:1867)
        at
    com.lombardisoftware.bpd.criticalpath.CriticalPath.processOutFlo
    w(CriticalPath.java:2198)
    .
    .---------------------------------------------
       This is due to a memory leak that frequently results in a
    java.lang.OutOfMemoryError.  The heap dump generated by
    that OutOfMemoryError (OOME) shows that the biggest chunk of
    heap space is taken up by the following array.
    .
    1,225,589,928 (16.03%) [39,384] 5,058 array of java/lang/Object
    0x78119c2a0
     1,148,800 (0.02%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData 0x760fdee70
     930,040 (0.01%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData 0x75f374af0
     294,400 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x73d8e7f30
     294,208 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7148d8cd0
     293,384 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7148d8cb8
     292,696 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x70204f058
     292,456 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x73d8e7f18
     292,456 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x73d8e7e88
     292,264 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7148d8c28
     292,192 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x70204f040
     291,976 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x73c426200
     291,256 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7148d8d00
     290,824 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x725012a80
     290,752 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x70204efb0
     290,752 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x702a61690
     290,512 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x73c426158
     290,512 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x73c4261e8
     290,280 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x73d8e7e70
     290,248 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x70204ef98
     290,248 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x702a61678
    There are 5,038 more children
    ,
    .---------------------------------------------------
    and also
    .
    1,090,915,472 (14.26%) [88,584] 5,179 array of java/lang/Object
    0x78c4adba0
     1,171,824 (0.02%) [48] 1
    com/ibm/xml/xlxp2/jaxb/model/PropertyTypeInformation 0x7b56ec968
     996,504 (0.01%) [40] 1 array of
    org/mozilla/javascript/ScriptableObject$Slot 0x79338c3d0
     539,128 (0.01%) [40] 1 array of org/jdom/Content 0x7b5807a88
     498,000 (0.01%) [64] 1 com/ibm/xml/xlxp2/grammar/Element
    0x7b329c0e0
     498,000 (0.01%) [64] 1 com/ibm/xml/xlxp2/grammar/Element
    0x7b31919b0
     486,288 (0.01%) [40] 6
    com/lombardisoftware/client/persistence/TWProcessConnectionPort
    0x78f33bc38
     305,976 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7184e8dc8
     304,032 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7184e8d20
     303,480 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7184e8db0
     302,016 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7184e8d08
     301,584 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7184e8f18
     301,584 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7184e8df8
     301,264 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x70cf845f8
     299,640 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x70cf84550
     299,640 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x7184e8f00
     299,544 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x70cf845e0
     298,896 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x73302a7f8
     298,392 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x73302a7e0
     297,696 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x70cf84538
     297,376 (0%) [24] 2
    com/lombardisoftware/data/criticalpath/CPPathData
    0x718a26898
    There are 5,159 more children
    

Local fix

Problem summary

  • When you go to the Process Instance dashboard or hover over an
    instance in the Process Performance dashboard, Process Portal
    might time out with a "Loading" message because of the time it
    takes to retrieve the projected path. Additionally, a large
    amount of CPU is used on the server, which might result in an
    OutOfMemoryError.
    
    EDITIONS AFFECTED:
    IBM Business Process Manager (BPM) V8.5.0.1 Advanced, Standard,
    and Express
    
    
    PROBLEM DETAILED DESCRIPTION:
    For some complex BPDs, such as BPDs with parallel looping paths
    and BPDs with many path permutations, distinct paths from the
    start to end nodes cannot be found. In these cases, the server
    might take a long time and might exhaust resources trying to
    find the distinct paths for the projected path.
    

Problem conclusion

  • A fix for IBM BPM V8.5.0.1 is available that adds a configurable
    timeout value for how long the server will try to determine the
    projected path:
    
    <common>
      <critical-path>
        <!-- Limits the amount of time the system spends trying to
    calculate the critical path, in seconds  -->
        <calc-all-paths-processing-time-limit
    merge="replace">20</calc-all-paths-processing-time-limit>
      </critical-path>
    </common>
    
    When the timeout value is not set in the configuration, the
    server spends 20 seconds trying to find the projected path. You
    can override the timeout value in the 100Custom.xml file. If the
    server times out, the projected path, future projected tasks,
    and estimated completion time are not displayed.  Subsequent
    requests for projected paths on the same BPD will return
    immediately, the server will not attempt to determine the
    projected path if it exhausted the timeout on a previous
    attempt.
    
    Additionally, when there are no completed instances for a BPD, a
    Process Performance dashboard message in the SystemOut.log file
    has been changed from "EXCEPTION WHILE INITIALIZING STAT
    LIBRARY" to "WARNING: Could not retrieve data for the completed
    instances. Either there are no completed instances for the BPD
    or there was an exception initializing the stat library."
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR49413:
    
     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 JRxxxxx, 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

Comments

APAR Information

  • APAR number

    JR49413

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-20

  • Closed date

    2014-04-07

  • Last modified date

    2015-04-12

  • 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 ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
12 April 2015