IBM Support

JR58508: OUTOFMEMORY CONDITION WHEN USING PROJECT PATH MANAGEMENT ON COMPLEX BPDS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Complex BPDs might cause an OutOfMemory condition in terms of
    the Projected Path Management. A heapdump analysis will show a
    pattern like:
    ----------------------------------------------------------------
    --------
    287,444,768 (9%) [48] 1 java/util/HashMap 0x15dd1b1c0
        287,444,720 (9%) [32,784] 3,407 array of
    java/util/HashMap$Entry 0x1800502b0
            659,160 (0%) [24] 3 java/util/HashMap$Entry 0x1a1f7b608
      379,040 (0%) [24] 3 java/util/HashMap$Entry 0x193ce0000
                    251,296 (0%) [136] 6
    com/lombardisoftware/data/criticalpath/CPNode 0x193cdfc78
                        209,136 (0%) [24] 1 java/util/ArrayList
    0x193cdfd18
                            209,112 (0%) [56] 5 array of
    java/lang/Object 0x1955e1da8
                                41,816 (0%) [24] 1 java/lang/String
    0x1955e1d90
                                    41,792 (0%) [41,792] 0 char[]
    0x1955d7a58
                                41,816 (0%) [24] 1 java/lang/String
    0x1956014b0
                                41,808 (0%) [24] 1 java/lang/String
    0x1955ec108
                                41,808 (0%) [24] 1 java/lang/String
    0x1955f7160
                                41,808 (0%) [24] 1 java/lang/String
    0x19560c428
                        41,896 (0%) [24] 1 java/util/ArrayList
    0x193cdfd00
                        128 (0%) [24] 1 java/util/ArrayList
    0x193cdfd30
                        41,808 (0%) [24] 1 java/lang/String
    0x193cdfc60
                        41,712 (0%) [24] 1 java/lang/String
    0x194712ee8
                        There are 1 more children
                    127,720 (0%) [24] 3 java/util/HashMap$Entry
    0x18c05d388
                    41,808 (0%) [24] 1 java/lang/String 0x193cdfc60
                280,096 (0%) [136] 6
    com/lombardisoftware/data/criticalpath/CPNode 0x1a1f7b280
                46,608 (0%) [24] 1 java/lang/String 0x1a1f7b268
            481,592 (0%) [24] 3 java/util/HashMap$Entry 0x1a7b26a98
            478,072 (0%) [24] 3 java/util/HashMap$Entry 0x1aaaea9e0
            475,032 (0%) [24] 3 java/util/HashMap$Entry 0x1a322b7e0
            469,768 (0%) [24] 3 java/util/HashMap$Entry 0x1a663c2e8
            There are 3,402 more children
    ----------------------------------------------------------------
    --------
    

Local fix

  • Disable the Projected Path Management for the BPD during
    Development time (Process Designer). Although this disable the
    functionality, it prevents unexpected crashs of the JVM.
    

Problem summary

  • When the Projected Path Management option is enabled for large
    BPDs, the JVM might crash with an OutOfMemoryError exception
    while calculating the path.
    

Problem conclusion

  • A fix will be available in a IBM BPM V8.6.0.0 CF2017.12 that
    stops calculating the path after an amount of time that you can
    customize in the 100Custom.xml file by using the following
    property (introduced by APAR JR49413):
    
    <common>
        <critical-path>
            <calc-all-paths-processing-time-limit
    
    merge="replace">20</calc-all-paths-processing-time-limit>
        </critical-path>
    </common>
    
    This property cancels the calculation of the critical path when
    the time limit is exceeded. Each additional attempt to calculate
    the path is skipped during the JVM lifetime. Because the
    calculation is done at the BPD level, complex paths requiring
    more memory are avoided whereas smaller BPDs might still be
    processed. Restarting the JVM causes another attempt to
    calculate the path for future BPD instances. Using this property
    also affects the displayed details in the Gantt Chart and the
    Set Path: for the Gantt Chart, what will be returned can't be
    predicted because the calculation was impeded; for the Set Path,
    the critical path is no longer shown on the diagram being
    displayed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR58508

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    857

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-29

  • Closed date

    2017-10-06

  • Last modified date

    2017-10-06

  • 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

  • R857 PSN

       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":"857","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 October 2017