Fixes are available
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
When the customer has create.sessions.when.listeners.exist enabled, they are getting NullPointerException. The stack is as follow. . java.lang.NullPointerException at com.ibm.ws.sip.container.servlets.OutgoingSipServletRequest.<ini t>(OutgoingSipServletRequest.java:270) at com.ibm.ws.sip.container.servlets.SipServletsFactoryImpl.createR equest(SipServletsFactoryImpl.java:456) at com.ibm.ws.sip.container.servlets.SipServletsFactoryImpl.createR equest(SipServletsFactoryImpl.java:592) at com.avaya.asm.callprocessing.userrelationshipelement.eventinghan dler.InternalESDistributor.createEventRequest ...
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All Session Initiation Protocol (SIP) * * container users of IBM WebSphere * * Application Server V8.0 * **************************************************************** * PROBLEM DESCRIPTION: NullPointerException when * * create.sessions.when.listeners.exist * * is enabled * **************************************************************** * RECOMMENDATION: * **************************************************************** When acting as a UAC and creating a new request for a new session and the CREATE.SESSIONS.WHEN.LISTENERS.EXIST is set to true the SIP container is trying to get the relevant SIP servlet object before it is set.
Problem conclusion
The SIP container is now getting the SIP servlet object after it is set. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.3. 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
PM52005
Reported component name
WAS EXPRESS
Reported component ID
5724I6300
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-10
Closed date
2011-11-21
Last modified date
2011-11-21
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
WAS EXPRESS
Fixed component ID
5724I6300
Applicable component levels
R800 PSY
UP
Document Information
Modified date:
28 October 2021