IBM Support

JR52648: WHEN YOU CHOOSE TO AUTOMATICALLY FLOW TO THE NEXT TASK IN BPD ACTIVITIES, YOU MIGHT EXPERIENCE OUT OF MEMORY ERRORS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you select ?Automatically flow to next task? in the user task
    activities of your business process definitions (BPDs) , you
    might experience heap growth and possibly
    java.lang.OutOfMemoryErrors.
    A heap dump shows that a large percentage of the heap is
    occupied by TaskSummaryResolver objects nested in a hash map in
    ExecutionContextRegistry, and the heap layout is similar to the
    following layout:
    Class Name                                     | Retained Heap |
    ----------------------------------------------------------------
    class com.lombardisoftware.component.common.workflow.
        ExecutionContextRegistry                   | 2,152,915,864 |
    |- java.util.HashMap                           | 2,152,915,600 |
    |  '- java.util.HashMap$Entry[8192]            | 2,152,915,552 |
    |     |- java.util.HashMap$Entry               |     2,853,856 |
    |     |  |- java.util.HashMap$Entry            |     2,052,344 |
    |     |  |- com.lombardisoftware.server.core.
              TaskSummaryResolver                  |       801,488 |
    |     |  '- Total: 2 entries                   |               |
    |     |- java.util.HashMap$Entry               |     2,767,544 |
    |     |  |- java.util.HashMap$Entry            |     1,687,384 |
    |     |  |- com.lombardisoftware.server.core.
              TaskSummaryResolver                  |     1,080,136 |
    |     |  '- Total: 2 entries                   |               |
    |     |  ...
    ----------------------------------------------------------------
    

Local fix

Problem summary

  • When IBM BPM runs activities that automatically flow to the next
    task, it creates a separate thread for each activity to perform
    the next steps following the completion of the activity. This
    special thread uses a java.lang.ThreadLocal variable that is not
    correctly freed when the thread ends. With each run of an
    activity that automatically flows to the next task, a data
    structure remains in the ThreadLocal variable that increases the
    used heap size.
    

Problem conclusion

  • A fix is available for IBM BPM that frees the ThreadLocal
    variable when the thread is complete.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR52648
    
    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 JR52648, 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 number

    JR52648

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-02-26

  • Closed date

    2015-04-17

  • Last modified date

    2015-04-17

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"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:
17 April 2015