PM52955: OUTBOUND SIP MESSAGE FAILS

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 Application Server
  
  [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 Feature    *
  *                  Pack for Communications Enabled             *
  *                  Applications (CEA)                          *
  ****************************************************************
  * 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 pack 1.0.0.13. 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 is sysrouted FROM one or more of the following:

  PM47418

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

Fix information

• Fixed component name

  CEA FEATUREPACK

• Fixed component ID

  5724J0855

Applicable component levels

• R700 PSY

     UP