Fixes are available
PM47418; 7.0.0.21: Outbound SIP Message Fails
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The following NPE is displayed in SystemErr.log file when a Session Initiation Protocol (SIP) application tries to send a SIP MESSAGE request to another application installed on the same instance of Websphere [8/22/11 23:19:29:267 EDT] 0000003f SystemErr R Exception in thread "Default : 4" java.lang.NullPointerException [8/22/11 23:19:29:267 EDT] 0000003f SystemErr R at com.ibm.ws.tcp.channel.impl.TCPWriteRequestContextImpl.write(TCP WriteRequestContextImpl.java:345) [8/22/11 23:19:29:267 EDT] 0000003f SystemErr R at com.ibm.ws.ssl.channel.impl.SSLUtils.handleHandshake(SSLUtils.ja va:760) [8/22/11 23:19:29:267 EDT] 0000003f SystemErr R at com.ibm.ws.ssl.channel.impl.SSLWriteServiceContext.doHandshake(S SLWriteServiceContext.java:545) [8/22/11 23:19:29:267 EDT] 0000003f SystemErr R at com.ibm.ws.ssl.channel.impl.SSLWriteServiceContext.write(SSLWrit eServiceContext.java:290) [8/22/11 23:19:29:267 EDT] 0000003f SystemErr R at com.ibm.ws.ssl.channel.impl.SSLWriteServiceContext$QueuedWork.ru n(SSLWriteServiceContext.java:854) [8/22/11 23:19:29:267 EDT] 0000003f SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Session Initiation Protocol (SIP) users * * of IBM WebSphere Application Server V7.0 * * and V8.0 * **************************************************************** * PROBLEM DESCRIPTION: Outbound messages are dropped. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem occurs when the SIP container is sending out messages over a connection that it created out, and then it closes this connection. In some edge cases it closes the connection before having sent all messages in the outbound queue.
Problem conclusion
With this fix, the SIP container closes the connection in two steps. First, it flags the connection as "closing down". In this state, messages that are already queued for delivery are processed, but no new messages are queued. Then, only after the last message is removed from the queue and sent out, it safely closes the connection down. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.23 and 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
PM47418
Reported component name
CEA FEATUREPACK
Reported component ID
5724J0855
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-08
Closed date
2011-12-05
Last modified date
2011-12-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PM52954 PM52955
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
06 January 2022