IBM Support

PI60893: DEADLOCK CAUSED BY SIP SUBSCRIBE

Fixes are available

8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
16.0.0.3: WebSphere Application Server Liberty 16.0.0.3
16.0.0.4: WebSphere Application Server Liberty 16.0.0.4
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
17.0.0.1: WebSphere Application Server Liberty 17.0.0.1
17.0.0.2: WebSphere Application Server Liberty 17.0.0.2
17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The third-party endpoints will occasionally send a second
    SUBSCRIBE as Session Management is sending the in-dialog NOTIFY.
    If the timing is just right, the threads processing the incoming
    SUBSCRIBE and the outgoing NOTIFY can deadlock.
    .
    Thread "SipContainerPool : 3" (0x0000000003FEA400)
    is waiting for:
    sys_mon_t:0x00007F51325727B0 infl_mon_t: 0x00007F5132572828:
    
    
    com/ibm/ws/sip/container/tu/TransactionUserImpl@0x00000007834BAA
    E0
    which is owned by:
    Thread "SipContainerPool : 13" (0x000000000307E800)
    which is waiting for:
    sys_mon_t:0x00007F51325710B8 infl_mon_t: 0x00007F5132571130:
    java/lang/Object@0x00000007802A56F8
    which is owned by:
    Thread "SipContainerPool : 3" (0x0000000003FEA400)
    .
    Stacks are as follow.
    .
    "SipContainerPool : 3"
    .
    at
    com/ibm/ws/sip/container/tu/TransactionUserImpl.generateLocalTag
    (TransactionUserImpl.java:3611(Compiled Code))
    (entered lock:
    com/ibm/ws/sip/container/tu/TransactionUserImpl@0x00000007834BAA
    E0, entry count: 1)
    at
    com/ibm/ws/sip/container/tu/TransactionUserWrapper.generateLocal
    Tag(TransactionUserWrapper.java:1076(Compiled Code))
    (entered lock: java/lang/Object@0x00000007802A56F8, entry
    count: 1)
    at
    com/ibm/ws/sip/container/servlets/OutgoingSipServletResponse.upd
    ateToTag(OutgoingSipServletResponse.java:490(Compiled Code))
    ...
    "SipContainerPool : 13"
    .
    at
    com/ibm/ws/sip/container/tu/TransactionUserWrapper.getNextCSeqNu
    mber(TransactionUserWrapper.java:1117(Compiled Code))
    at
    com/ibm/ws/sip/container/servlets/OutgoingSipServletRequest.<ini
    t>(OutgoingSipServletRequest.java:200(Compiled Code))
    at
    com/ibm/ws/sip/container/tu/TransactionUserImpl.createRequest(Tr
    ansactionUserImpl.java:921(Compiled Code))
    (entered lock:
    com/ibm/ws/sip/container/tu/TransactionUserImpl@0x00000007834BAA
    E0, entry count: 1)
    at
    com/ibm/ws/sip/container/tu/TransactionUserWrapper.createRequest
    (TransactionUserWrapper.java:587(Compiled Code))
    at
    com/ibm/ws/sip/container/servlets/SipSessionImplementation.creat
    eRequest(SipSessionImplementation.java:290(Compiled Code))
    ...
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Session Initiation Protocol (SIP)    *
    ****************************************************************
    * PROBLEM DESCRIPTION: A deadlock in the SIP Container when    *
    *                      handling an outgoing request and        *
    *                      response at the same time               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Deadlock can occur in the SIP container when an application
    handles an outgoing request and response at the same time
    

Problem conclusion

  • The SIP Container has been updated to resolve the
    syncronization issue to prevent the deadlock.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.10.  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

    PI60893

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-15

  • Closed date

    2016-05-20

  • Last modified date

    2016-05-20

  • 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":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021