IBM Support

PM33487: DEADLOCK IN SIP CONTAINER CODE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Deadlock seen in Session Initiation Protocol (SIP) Container
    code in WebSphere Application Server Feature Pack for
    Communications Enabled Applications (CEA).
    
    Ex:"Telephony Command Dispatcher 0" J9VMThread:0x47ECC300,
    j9thread_t:0x4AAF0838, java/lang/Thread:0x02BB1490, state:B,
    prio=5 (native thread ID:0x213C, native priority:0x5,native
    policy:UNKNOWN)
    
    
    Java callstack:at
    com/ibm/ws/sip/container/tu/TransactionUserWrapper.getApplicatio
    nSession(TransactionUserWrapper.java:977(Compiled Code))
    at
    com/ibm/ws/sip/container/servlets/SipSessionImplementation.getAp
    plicationSession(SipSessionImplementation.java:288(Compiled
    Code))
    at
    com/ibm/ws/sip/container/servlets/DRSSipSessionImpl.shouldBeRepl
    icated(DRSSipSessionImpl.java:201(Compiled Code))
    at
    com/ibm/ws/sip/container/failover/FailoverMgrImpl.replicate(Fail
    overMgrImpl.java:461(Compiled Code))
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All IBM WebSphere Application Server Feature*
    *                  Pack for Communications Enabled Applications*
    *                  (CEA) users                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deadlock seen in Session Initiation     *
    *                      Protocol (SIP) Container code           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When invalidating a SIP application session from a none SIP
    thread, locking of two Objects in a reverse order can cause a
    dead lock situation.
    

Problem conclusion

  • The SIP container is locking the same object even when the SIP
    application session access is done from a none SIP thread,
    this approach prevents the SIP container code from locking two
    objects in the reverse order
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 1.0.0.11. 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

    PM33487

  • Reported component name

    CEA FEATUREPACK

  • Reported component ID

    5724J0855

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-24

  • Closed date

    2011-03-01

  • Last modified date

    2011-03-01

  • APAR is sysrouted FROM one or more of the following:

    PM31742

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CEA FEATUREPACK

  • Fixed component ID

    5724J0855

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"700","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
09 February 2022