PM11625: MEMORY LEAK IN SIP CONTAINER DUE TO EXCEPTIONS THROWN WHILE SESSIONS ARE INVALIDATING

Fixes are available

APAR status

Closed as program error.

Error description

Memory leak in Session Initiation Protocol (SIP) container due
to exceptions thrown while sessions are invalidating

3/12/10 16:09:19:019 UTC] 0000548a WebApp        E   [Servlet
Error]-[exampleSipServlet]: java.lang.NullPointerException
at
com.ibm.ws.sip.container.util.SipUtil.setDestinationHeader(SipUt
il.java:460)
at
com.ibm.ws.sip.container.transaction.ClientTransaction.sendReque
st(ClientTransaction.java:137)
at
com.ibm.ws.sip.container.servlets.OutgoingSipServletRequest.send
(OutgoingSipServletRequest.java:639)
at
com.ibm.ws.sip.container.servlets.OutgoingSipServletRequest.send
(OutgoingSipServletRequest.java:604)
at
com.ibm.ws.sip.container.tu.TransactionUserImpl.terminateUnderly
ingTransaction(TransactionUserImpl.java:854)
at
com.ibm.ws.sip.container.tu.TransactionUserImpl.invalidateTU(Tra
nsactionUserImpl.java:801)
at
com.ibm.ws.sip.container.tu.TransactionUserWrapper.invalidateTU(
TransactionUserWrapper.java:1130)
at
com.ibm.ws.sip.container.servlets.SipApplicationSessionImpl.dest
royAllSessions(SipApplicationSessionImpl.java:485)
at
com.ibm.ws.sip.container.servlets.SipApplicationSessionImpl.inva
lidate(SipApplicationSessionImpl.java:549)
at
com.ibm.ws.sip.container.servlets.WASXSipApplicationSessionImpl.
invalidate(WASXSipApplicationSessionImpl.java:100)
at
com.att.as.sip.b2bua.B2buaSipServlet.doTermErrorResponse(B2buaSi
pServlet.java:1326)
at
com.att.as.sip.b2bua.B2buaSipServlet.doErrorResponse(B2buaSipSer
vlet.java:822)
at javax.servlet.sip.SipServlet.doResponse(SipServlet.java:563)
at
com.att.as.sip.b2bua.B2buaSipServlet.doResponse(B2buaSipServlet.
java:5197)
at
javax.servlet.sip.SipServlet.doResponseWrapper(SipServlet.java:7
94)
at javax.servlet.sip.SipServlet.service(SipServlet.java:198)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1075)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWr
apper.java:1016)
at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
FilterChain.java:145)
at
com.ibm.ws.sip.container.was.SipFilter.doFilter(SipFilter.java:1
13)
at
com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(Fi
lterInstanceWrapper.java:190)
at
com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebApp
FilterChain.java:130)
at
com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAp
pFilterChain.java:87)
at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA
ppFilterManager.java:771)
at
com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebA
ppFilterManager.java:679)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(Ser
vletWrapper.java:546)
at
com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(S
ervletWrapper.java:478)
at
com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleReques
t(CacheServletWrapper.java:90)
at
com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.
java:744)
at
com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContaine
r.java:1455)
at
com.ibm.wsspi.webcontainer.WebContainer.handleRequest(WebContain
er.java:91)
at
com.ibm.ws.sip.container.was.SipMessage.dispatch(SipMessage.java
:1321)
at
com.ibm.ws.sip.container.was.SipMessage.run(SipMessage.java:1292
)
at
com.ibm.ws.sip.container.was.WebsphereInvoker.invokeSipServlet(W
ebsphereInvoker.java:141)
at
com.ibm.ws.sip.container.router.SipRouter.invokeSipServlet(SipRo
uter.java:709)
at
com.ibm.ws.sip.container.tu.TransactionUserImpl.sendResponseToAp
plication(TransactionUserImpl.java:1546)
at
com.ibm.ws.sip.container.tu.TransactionUserImpl.processResponse(
TransactionUserImpl.java:2044)
at
com.ibm.ws.sip.container.tu.TransactionUserWrapper.processRespon
se(TransactionUserWrapper.java:429)
at
com.ibm.ws.sip.container.transaction.ClientTransaction.responseR
eceived(ClientTransaction.java:223)
at
com.ibm.ws.sip.container.naptr.Sender.responseReceived(Sender.ja
va:56)
at
com.ibm.ws.sip.container.transaction.ClientTransaction.processRe
sponse(ClientTransaction.java:179)
at
com.ibm.ws.sip.container.router.tasks.ResponseRoutedTask.doTask(
ResponseRoutedTask.java:60)
at
com.ibm.ws.sip.container.router.tasks.RoutedTask.run(RoutedTask.
java:78)
at
com.ibm.ws.sip.container.was.SignalingEndOfTask.run(SignalingEnd
OfTask.java:43)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0                        *
****************************************************************
* PROBLEM DESCRIPTION: Memory leak in Session Initiation       *
*                      Protocol (SIP) container due to         *
*                      exceptions thrown while sessions are    *
*                      invalidating                            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
An exception is thrown:
3/12/10 16:09:19:019 UTC] 0000548a WebApp        E   [Servlet
Error]-[exampleSipServlet]: java.lang.NullPointerException
at
com.ibm.ws.sip.container.util.SipUtil.setDestinationHeader(SipUt
il.java:460)
at
com.ibm.ws.sip.container.transaction.ClientTransaction.sendReque
st(ClientTransaction.java:137)

This occurs when the container is attempting to cancel an early
transaction of a session that the application has invalidated.
The reason for this was that the session was not in the
correct state, according to the state machine defined in the
JSR and RFC.

Problem conclusion

The code was changed so that any response with code greater
then 300 will transition the session state back to the initial
state, as the specification instructs.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.13 and 6.1.0.33 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
PM11625
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-07
Closed date
2010-06-17
Last modified date
2010-06-17

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

PM15024

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM11625: MEMORY LEAK IN SIP CONTAINER DUE TO EXCEPTIONS THROWN WHILE SESSIONS ARE INVALIDATING

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?