IBM Support

JR53701: DEADLOCK OCCURS FOR RESOURCE BORESOURCELOCATOR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If your IBM Business Process Manager (BPM) server is running a
    heavy load, the server might deadlock and you might see an
    error message in the the javacore file that is similar to the
    following error message:
    
    1LKDEADLOCK    Deadlock detected !!!
    NULL           ---------------------
    NULL
    2LKDEADLOCKTHR  Thread "WorkManager.bpm-em-workmanager : 1"
    (0x0000000046C50300)
    3LKDEADLOCKWTR    is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x00000100185C4858 infl_mon_t:
    0x00000100185C48A0:
    4LKDEADLOCKOBJ
    com/ibm/ws/box/BOResourceLocator@0x000000058BA23750
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "WorkManager.bpm-em-workmanager : 0"
    (0x0000000046B60A00)
    3LKDEADLOCKWTR    which is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x0000010033D12458 infl_mon_t:
    0x0000010033D124A0:
    4LKDEADLOCKOBJ
    com/ibm/xml/xci/type/TypeRegistry@0x0000000589ECF000
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "WorkManager.bpm-em-workmanager : 1"
    (0x0000000046C50300)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM BPM Advanced Edition                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: If your IBM Business Process Manager    *
    *                      (BPM) server is running a heavy load,   *
    *                      the server might deadlock and you       *
    *                      might see an error message in the the   *
    *                      javacore file that is similar to the    *
    *                      following error message:                *
    *                      1LKDEADLOCK    Deadlock detected !!!    *
    *                      NULL           ---------------------    *
    *                      NULL                                    *
    *                      2LKDEADLOCKTHR  Thread                  *
    *                      "WorkManager.bpm-em-workmanager : 1"    *
    *                      (0x0000000046C50300)                    *
    *                      3LKDEADLOCKWTR    is waiting for:       *
    *                      4LKDEADLOCKMON                          *
    *                      sys_mon_t:0x00000100185C4858            *
    *                      infl_mon_t:                             *
    *                      0x00000100185C48A0:                     *
    *                      4LKDEADLOCKOBJ                          *
    *                      com/ibm/ws/box/BOResourceLocator@0x0000 *
    *                      00058BA23750                            *
    *                      3LKDEADLOCKOWN    which is owned by:    *
    *                      2LKDEADLOCKTHR  Thread                  *
    *                      "WorkManager.bpm-em-workmanager : 0"    *
    *                      (0x0000000046B60A00)                    *
    *                      3LKDEADLOCKWTR    which is waiting      *
    *                      for:                                    *
    *                      4LKDEADLOCKMON                          *
    *                      sys_mon_t:0x0000010033D12458            *
    *                      infl_mon_t:                             *
    *                      0x0000010033D124A0:                     *
    *                      4LKDEADLOCKOBJ                          *
    *                      com/ibm/xml/xci/type/TypeRegistry@0x000 *
    *                      0000589ECF000                           *
    *                      3LKDEADLOCKOWN    which is owned by:    *
    *                      2LKDEADLOCKTHR  Thread                  *
    *                      "WorkManager.bpm-em-workmanager : 1"    *
    *                      (0x0000000046C50300)                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    This issue is caused by multiple threads loading the same
    resource or different resources in the same scope at the same
    time, otherwise known as a  óÔé¼ ôresource race óÔé¼  ¢.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.0.1 that fixes the program
    error that occurs when a business object loads the resources.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR53701:
    
    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 JR53701, 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

    JR53701

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-26

  • Closed date

    2015-09-16

  • Last modified date

    2015-09-16

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 August 2023