Fixes are available
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
Overload error response code needs to be configurable.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IBM WebSphere Application Server version * * 6.1 users of the Session Initiation Protocol * * (SIP) Proxy who enable the overload feature. * **************************************************************** * PROBLEM DESCRIPTION: We need to make our "overload SIP * * response" configurable * **************************************************************** * RECOMMENDATION: * **************************************************************** Users want to control the error response during an overload situation
Problem conclusion
The SIP proxy can be configured to detect overload situations. When the proxy is configured for "overload protection", it monitors the amount of traffic processed at the proxy and limits the number of new requests. If overload occurs, it rejects some SIP requests with an error response. By default, the proxy responds with a "503 Service Unavailable" response. Some customers prefer to use a different error response. So, we made the response configurable. In the administrative console, you can set the overload "status code" and "reason phrase" via custom properties. These properties can be added to the SIP Proxy custom property settings to change the response: overloadResponseCode (by default, 503) overloadResponseReasonPhrase (by default, "Service Unavailable"). The fix for this APAR is currently targeted for inclusion in release 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 An iFix of this defect is available on request.
Temporary fix
Comments
APAR Information
APAR number
PK50952
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-08-13
Closed date
2007-10-01
Last modified date
2007-10-01
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
Document Information
Modified date:
29 December 2021