IBM Support

JR50003: PERFORMANCE ISSUE CAUSED BY BPM MULTIPLE CACHE RESETS DURING DEPLOYMENT (CacheManager.doRest()) RESULTING IN WSVR0605W

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In a clustered IBM Business Process Manager (BPM) environment,
    caches are reset multiple times in all cluster members when
    process applications that have many groups are deployed. As a
    result, IBM BPM performance is significantly affected.
    This fix supersedes JR49408.
    In the SystemOut.log or JavaCore files, you may see the
    following hung thread (WSVR0605W)
     Thread "SIBJMSRAThreadPool : 19" (00000036) has been active
    for 686707 milliseconds and may be hung.  There is/are 9
    thread(s) in total in the server that may be hung.
    at
    com.lombardisoftware.core.cache.LocalCache.resetCache(LocalCache
    .java:196)
    at
    com.lombardisoftware.servlet.util.CacheManager.doReset(CacheMana
    ger.java:225)
    at
    com.lombardisoftware.server.ejb.cache.CacheRequestListenerCore$P
    roxyCacheManager.doReset(CacheRequestListenerCore.java:96)
    at
    com.lombardisoftware.server.ejb.cache.CacheMessengerCore.process
    CacheCommand(CacheMessengerCore.java:90)
    at
    com.lombardisoftware.server.ejb.cache.CacheRequestListenerCore.o
    nMessage(CacheRequestListenerCore.java:67)
    

Local fix

  • n/a
    

Problem summary

  • When you create a new group, such as when you deploy a
    snapshot, group-related caches are reset and one of the caches
    is reloaded with all the available groups. If the number of
    groups is large, a significant performance degradation occurs.
    

Problem conclusion

  • A fix is/will be available that avoids unnecessary cache resets
    when  groups are created. In addition, no caches are preloaded
    for any of the group-related caches.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR50003:
    
    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 JR50003, 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

    JR50003

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-16

  • Closed date

    2014-07-09

  • Last modified date

    2015-04-24

  • 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

  • R751 PSY

       UP

  • R801 PSY

       UP

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

Document Information

Modified date:
24 April 2015