PK50039: IF THE PROXY IS STARTED UNDER HEAVY LOAD, IT IS POSSIBLE THAT IT WILL NOT ROUTE TRAFFIC CORRECTLY.

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• There is a sychronization issue at startup of the SIP proxy that
  causes the outbound UDP channel chain to not properly startup i
  f the SIP proxy is under load at the time.  This causes the SIP
  proxy to not publish its endpoint information to the SIP con
  tainers which causes the SIP containers to not send any data thr
  ough this proxy.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IBM WebSphere Application Server version *
  *                 6.1 Session Initiation Protocol (SIP) users  *
  ****************************************************************
  * PROBLEM DESCRIPTION: If the proxy is started under heavy     *
  *                      load, it is possible that it will not   *
  *                      route traffic correctly.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If you are starting your proxy under heavy load, this
  problem could be a major issue.  Incoming and outgoing
  messages may not be routed properly.
  

Problem conclusion

• There is a sychronization issue at startup of the SIP proxy
  that causes the outbound UDP channel chain to not properly
  startup if the SIP proxy is under load at the time. This
  causes the SIP proxy to not publish its endpoint information
  to the SIP containers which causes the SIP containers to not
  send any data through this proxy.
  
  This is fixed in fixpack 6.1.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:

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

Modules/Macros

• SIPPROXY
  

Fix information

• Fixed component name

  WEBSPH APP SERV

• 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