PM82550: DEADLOCK IN SESSION INITIATION PROTOCOL (SIP) CONTAINER

Fixes are available

APAR status

Closed as program error.

Error description

WebSphere logs show deadlock in the SIP Container threads.
The application server may crash with an out of memory error
(OOM) and many hung threads were detected in the SIP Container.
Deadlock detected !!!
---------------------
 Thread "Thread-60" (0xB1689000)
 is waiting for:
 sys_mon_t:0xAD657FB8 infl_mon_t: 0xAD657FF0:
 java/lang/Object@0xBC187CD8/0xBC187CE4:
 which is owned by:
 Thread "SipContainer : 1" (0xAE298D00)
 which is waiting for:
 sys_mon_t:0xAD658108 infl_mon_t: 0xAD658140:

com/ibm/ws/sip/container/proxy/StatefullProxy@0xBC1976A0/0xBC197
6AC:
 which is owned by:
 Thread "Thread-60" (0xB1689000)


"Thread-60" J9VMThread:0xB1689000, j9thread_t:0x09926EE0,
java/lang/Thread:0xB886D978, state:B, prio=5
 (native thread ID:0x62E9, native priority:0x5, native
policy:UNKNOWN)
 (native stack address range from:0xABB7A000, to:0xABBBB000,
size:0x41000)
 Java callstack:
 at
com/ibm/ws/sip/container/tu/TransactionUserWrapper.addToTransact
 at
com/ibm/ws/sip/container/proxy/StatefullProxy.onSendingRequest
 at
com/ibm/ws/sip/container/proxy/ProxyBranchImpl.onSendingRequest
 at
com/ibm/ws/sip/container/transaction/ClientTransaction.sendReque
 at
com/ibm/ws/sip/container/servlets/OutgoingSipServletRequest.send
 at
com/ibm/ws/sip/container/proxy/BranchManager.cancelRequest
 at
com/ibm/ws/sip/container/proxy/ProxyBranchImpl.cancel
 at
com/ibm/ws/sip/container/proxy/ProxyBranchImpl.cancel
 at
com/ibm/ws/sip/container/proxy/ProxyBranchImpl.executeTimeOut
 at
com/ibm/ws/sip/container/proxy/ProxyBranchImpl.proxyTimedOut
 at
com/ibm/ws/sip/container/proxy/BranchManager.timeoutAllChildBran
 at
com/ibm/ws/sip/container/proxy/StatefullProxy.proxyTimeout
 at
com/ibm/ws/sip/container/proxy/ProxyTimer.invoke
 at
com/ibm/ws/sip/container/timer/SipTimerTask.run
 at
java/util/Timer$TimerImpl.run



"SipContainer : 1" J9VMThread:0xAE298D00,
j9thread_t:0xAF0AFF18,
java/lang/Thread:0xC40BA7A0, state:B, prio=5
 (native thread ID:0x624E, native priority:0x5, native
policy:UNKNOWN)
 (native stack address range from:0xAC1BB000, to:0xAC1FC000,
size:0x41000)
 Java callstack:
 at

com/ibm/ws/sip/container/servlets/OutgoingSipServletResponse.con
 at
com/ibm/ws/sip/container/servlets/OutgoingSipServletResponse.sen
 at
com/ibm/ws/sip/container/tu/TransactionUserImpl.terminateUnderly
 at
com/ibm/ws/sip/container/tu/TransactionUserImpl.invalidateTU
 at
com/ibm/ws/sip/container/tu/TransactionUserWrapper.invalidateTU
 at
com/ibm/ws/sip/container/tu/TransactionUserWrapper.invalidateTU
 at
com/ibm/ws/sip/container/servlets/SipApplicationSessionImpl.dest
 at
com/ibm/ws/sip/container/servlets/SipApplicationSessionImpl.inva
 at
com/ibm/ws/sip/container/servlets/WASXSipApplicationSessionImpl.
 at
com/ibm/ws/sip/container/timer/AppSessionTimerListener.invokeExp
 at
com/ibm/ws/sip/container/timer/ExpirationTimer.run
 at
com/ibm/ws/sip/container/was/SignalingEndOfTask.run
 at
com/ibm/ws/util/ThreadPool$Worker.run

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Session Initiation Protocol (SIP)    *
****************************************************************
* PROBLEM DESCRIPTION: Deak lock in SIP cotnainer              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When session timout fired at the same time as Proxy timeout -
the events are not running on the same thread.

Problem conclusion

Code has been updated to correct the deadlock.
The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.25, 8.0.0.7 and the fix pack following
8.5.0.2. 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
PM82550
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
2013-02-11
Closed date
2013-03-25
Last modified date
2013-06-11

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
R800 PSY
UP
R850 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:
29 October 2021

Tips

PM82550: DEADLOCK IN SESSION INITIATION PROTOCOL (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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?