PM34709: DEADLOCK IN THE SIP CONTAINER

Fixes are available

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

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?rs=180&uid=swg27004980

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

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

Document Information

Modified date:
27 October 2021

Tips

PM34709: DEADLOCK IN THE SIP CONTAINER

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?