PM34709; 7.0.0.17: deadlock in the SIP container

Download Description

PM34709 resolves the following problem:

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:
None

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:
The bug is fixed in the SIP container transport layer.

The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.19. Please refer to the Recommended Updates page for delivery information:http://www.ibm.com/support/docview.wss?uid=swg27004980