IBM Support

JR50233: OUT OF MEMORY ERRORS OCCUR WHEN MIGRATING A LARGE NUMBER OF PROCESS INSTANCES USINGS THE MULTI-THREADING FEATURE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Out of memory errors occur when you migrate a large number of
    process instances by using the multi-threading feature. The
    number of instances that can be handled depends on the JVM heap
    size, but likely would be over 100K.
    
    When analyzing the heap dump from one of these occurrence the
    leak suspect or object holding majority of the space would be
    this:
    com.lombardisoftware.instrumentation.core.ThreadInstrumentation
    

Local fix

  • You can avoid this issue by setting enabled to false, which
    disables the instrumentationfor the Process Server, in the
    <properties> <server> <instrumentations> section:
    
    <process-monitor>
      <enabled>true</enabled>
      <max-inactive-process-units>100</max-inactive-process-units>
      <max-inactive-service-units>500</max-inactive-service-units>
    </process-monitor>
    

Problem summary

  • Because instrumentation logs are created for each migrated
    instance, the logging object eventually becomes large enough to
    cause GC(Garbage Collection) thrashing. The object that would
    take up the majority of the heap is
    com.lombardisoftware.instrumentation.core.ThreadInstrumentation.
    
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    

Problem conclusion

  • A fix is available for IBM BPM V8.0.1.2 that prevents the
    excessive instrumentation logging during instance migration and
    prevent the ThreadInstrumentation object from becoming too
    large.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR50233:
    
    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 JR50233, 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

    JR50233

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    801

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-14

  • Closed date

    2014-07-22

  • Last modified date

    2015-01-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

  • R801 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.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
12 January 2015