IBM Support

PI12131: DEADLOCK WHEN ACCESSING SESSION ATTRIBUTES DURING SESSION TIMEOUT IN SIP CONTAINER CODE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Deadlock when accessing Session attributes during session
    timeout in SIP container Code.
    ***********
    1LKDEADLOCK    Deadlock detected !!!
    NULL           ---------------------
    2LKDEADLOCKTHR  Thread "SipContainerPool : 2"
    (0x0000000003CA3A00)
    3LKDEADLOCKWTR    is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x00007F2631941038 infl_mon_t:
                                  0x00007F26319410B0:
    4LKDEADLOCKOBJ      java/lang/Object@0x00000007180F3258
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "SipContainerPool : 9"
    (0x0000000003B60B00)
    3LKDEADLOCKWTR    which is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x00007F262FE3AB68 infl_mon_t:
                                  0x00007F262FE3ABE0:
    4LKDEADLOCKOBJ
    com/ibm/ws/sip/container/servlets/DRSSipSessionImpl
                        @0x00000007180F1B28
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "SipContainerPool : 2"
    (0x0000000003CA3A00)
    NULL
    *********************
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 Session Initiation Protocol     *
    *                  (SIP) container                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: A deadlock is detected when accessing   *
    *                      session attributes during session       *
    *                      timeout in SIP Container code           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A deadlock is possible in SIP Container code when a session is
    expired, since there might be a concurrency of two threads of
    the same application session.
    

Problem conclusion

  • There was a bug in the thread that handles session expiration
    of an application session, that enabled a concurrency which led
    to a deadlock.
    The bug is fixed in this APAR, and the deadlock is no longer
    possible.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.3.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI12131

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-20

  • Closed date

    2014-03-04

  • Last modified date

    2014-03-04

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 April 2022