IBM Support

PM34709: DEADLOCK IN THE SIP CONTAINER

Fixes are available

PM34709; 7.0.0.17: deadlock in the SIP container
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • [3/11/11 15:11:57:566 EST] 00000020 SystemErr     R  at
    com.ibm.ws.sip.stack.transaction.transport.connections.channelfr
    amework.SipOutboundConnLink.ready(SipOutboundConnLink.java:75)
    [3/11/11 15:11:57:566 EST] 00000020 SystemErr     R  at
    com.ibm.ws.tcp.channel.impl.TCPConnLink.connectComplete(TCPConnL
    ink.java:343)
    [3/11/11 15:11:57:566 EST] 00000020 SystemErr     R  at
    com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptConnectWork(
    WorkQueueManager.java:928)
    [3/11/11 15:11:57:566 EST] 00000020 SystemErr     R  at
    com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueue
    Manager.java:1012)
    [3/11/11 15:11:57:566 EST] 00000020 SystemErr     R  at
    com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueu
    eManager.java:1071)
    [3/11/11 15:11:57:567 EST] 00000020 SystemErr     R  at
    com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Session Initiation Protocol (SIP) users     *
    *                  of IBM WebSphere Application Server V7.0    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The SIP container threads enter a       *
    *                      deadlock situation, preventing message  *
    *                      processing.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem occurs when a SIP connection gets closed down, and
    meanwhile, the SIP container attempts to send out a message on
    that same connection. Two threads are involved - one that
    detects the failure, and one that attempts to send out the
    message. If the two actions run concurrently, then each thread
    waits for the other to complete, introducing a deadlock.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM34709

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-13

  • Closed date

    2011-04-07

  • Last modified date

    2011-04-07

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM34709

Modified date: 07 April 2011