IBM Support

JR54004: PURGING MANY TASKS OR INSTANCES MIGHT CAUSE OUT OF MEMORY ERROR ON NODES PROCESSING TASK AND INSTANCE INDEXING INFORMATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An OutOfMemory error might occur when you purge of a large
    number of tasks and instances from IBM Business Process Manager
    (BPM) nodes that process task and instance indexing information.
       These are some exceptions you may see in the log
    [3/2/16 17:59:18:019 CET]     FFDC
    Exception:java.lang.OutOfMemoryError
    SourceId:com.ibm.ws.asynchbeans.J2EEContext.run ProbeId:394
    Reporter:com.ibm.ws.asynchbeans.J2EEContext@364e018c
    java.lang.OutOfMemoryError: Java heap space
     at java.util.Calendar.<init>(Calendar.java:945)
     at
    java.util.GregorianCalendar.<init>(GregorianCalendar.java:585)
     at
    java.util.GregorianCalendar.<init>(GregorianCalendar.java:552)
     at
    com.ibm.bpm.search.persistence.spi.impl.AbstractPersistenceManag
    er.getGregorianCalendarFromUTCTimestamp(AbstractPersistence
    Manager.java:238)
     at
    com.ibm.bpm.search.persistence.spi.impl.AbstractTaskIndexPM.buil
    dTaskIndex(AbstractTaskIndexPM.java:112)
     at
    com.ibm.bpm.search.persistence.spi.impl.AbstractTaskIndexPM.list
    PendingTaskIndexDeletions(AbstractTaskIndexPM.java:597)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessIndexBatchHelper.remo
    veOrphanProcessIndexEntries(ProcessIndexBatchHelper.java:502)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessSearchIndexerImpl.rem
    oveOrphanProcessIndexEntries(ProcessSearchIndexerImpl.
    java:2333)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessIndexUpdaterDaemon.pr
    ocessTaskChangeMessages(ProcessIndexUpdaterDaemon.java:686)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessIndexUpdaterDaemon.pe
    rformActiveWork(ProcessIndexUpdaterDaemon.java:246)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessIndexUpdaterDaemon.ru
    nActive(ProcessIndexUpdaterDaemon.java:204)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessIndexUpdaterDaemon.ru
    n(ProcessIndexUpdaterDaemon.java:138)
    
    [3/4/16 0:48:26:750 CET]     FFDC
    Exception:java.lang.OutOfMemoryError
    SourceId:com.ibm.ws.asynchbeans.J2EEContext.run ProbeId:394
    Reporter:com.ibm.ws.asynchbeans.J2EEContext@34aa3925
    java.lang.OutOfMemoryError: Java heap space
     at java.lang.Long.valueOf(Long.java:568)
     at
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO.<init>(TaskI
    ndexVO.java:61)
     at
    com.ibm.bpm.search.persistence.spi.impl.AbstractTaskIndexPM.buil
    dTaskIndex(AbstractTaskIndexPM.java:114)
     at
    com.ibm.bpm.search.persistence.spi.impl.AbstractTaskIndexPM.list
    PendingTaskIndexDeletions(AbstractTaskIndexPM.java:597)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessIndexBatchHelper.remo
    veOrphanProcessIndexEntries(ProcessIndexBatchHelper.java:502)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessSearchIndexerImpl.rem
    oveOrphanProcessIndexEntries(ProcessSearchIndexerImpl.
    java:2333)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessIndexUpdaterDaemon.pr
    ocessTaskChangeMessages(ProcessIndexUpdaterDaemon.java:686)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessIndexUpdaterDaemon.pe
    rformActiveWork(ProcessIndexUpdaterDaemon.java:246)
     at
    com.ibm.bpm.search.process.spi.impl.ProcessIndexUpdaterDaemon.ru
    nActive(ProcessIndexUpdaterDaemon.java:204)
    
       There are a large number of this object on the heap
    java.util.ArrayList @ 0x719d3de70
    24 3,300,142,144 88.36%
    \
    java.lang.Object[2872626] @ 0x7e08a2fa8
    11,490,520 3,300,142,120 88.36%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a079f0 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07a28 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07a60 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07a98 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07ad0 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07b08 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07b40 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07b78 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07bb0 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07be8 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07c20 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07c58 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07c90 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07cc8 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07d00 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07d38 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07d70 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07da8 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07de0 56 1,560 0.00%
    .+
    com.ibm.bpm.search.persistence.spi.impl.TaskIndexVO @
    0x796a07e18 56 1,560 0.00%
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    

Local fix

Problem summary

  • When you use the BPMProcessInstancesCleanup wsadmin command to
    purge tasks and instances from the database, the next time the
    IBM Process Portal indexer runs (automatically, during the next
    indexing interval), the indexer tries to delete those tasks and
    instances from the Process Portal index in one transaction. As a
    result, the deletion might use enough heap memory to cause an
    out of memory error.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.5.0 that splits the deletion
    of tasks and instances from the Process Portal index into
    batches of 5000 per transaction, limiting the heap usage and
    reducing the likelihood of an out of memory error.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR54004.
    
     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 JR54004, 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

    JR54004

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-04

  • Closed date

    2015-12-11

  • Last modified date

    2016-04-01

  • 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

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

Document Information

Modified date:
01 April 2016