PI26198: SIP Container does not recognize that SIP Proxy is available.

8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Under certain scenarios an issue may occur where when
  one of the WebSphere SIP proxy servers is stopped and the below
  error is seen:
  ASND0003I: Detected server <name> stopped on node <node>
  
  The application server on the node is aware that the proxy
  server is not running. However, when the SIP Container needs to
  send a message, it still tries to communicate with that
  WebSphere SIP proxy server and  fails as expected. As a result,
  a message can't be sent to the destination.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5 who use Session Initiation      *
  *                  Protocol (SIP) on Network Deployment        *
  *                  edition.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Under certain timing scenarios, the SIP *
  *                      Container does not recognize that a SIP *
  *                      Proxy is available to transmit outbound *
  *                      messages.   This results in errors at   *
  *                      the                                     *
  *                      SIP Container.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The SIP Container receives notifications about SIP Proxy
  startup from two different notification mechanisms. These
  normally occur in a set order. If these notifications occur
  out of order, the SIP Container will not realize that the SIP
  Proxy is available.
  

Problem conclusion

• We made changes to the SIP Container and SIP Proxy to retry
  the startup notification if they occur out of order. To enable
  this fix, add this custom property to the SIP Proxy,
  "startupRetryInterval=4000"
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.6.  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:

• 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

• R850 PSY

     UP