Fixes are available
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
In case of a parse error in any of the SIP messages, the TCP connection to the container is dropped. Behind the TCP connection, could be hundreds of clients. Thus, all the clients would be affected.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Session Initiation Protocol (SIP) * * Container * **************************************************************** * PROBLEM DESCRIPTION: In case of a parse error in any of * * the SIP messages, the TCP * * connection to the container is * * dropped. * **************************************************************** * RECOMMENDATION: * **************************************************************** In case of a parse error in any of the SIP messages, the TCP connection to the container is dropped. Behind this TCP connection, could be hundreds of clients. Thus, all the clients would be affected.
Problem conclusion
The fix for is tolerant to parse errors: Each reliable connection has a parse error counter. The parse error counter is initialized when the connection is established. In addition, each connection has a timer listener. When the timer listener is fired, the parse error counter is set to 0 and the timer starts again. The fix is enabled by 3 new custom properties: CP name: number.of.parse.errors.allowed Description: Specifies the number of allowed parse errors before closing a reliable connection. -1 indicates never close the reliable connection on any parse error. 0 indicates closing the reliable connection on any parse error i.e. at least 1 parse error. 1 indicates closing the reliable connection on at least 2 parse errors. In general, (n) indicates closing the reliable connection on at least (n+1) parse errors. Data Type: String Default: 0 CP name: parse.errors.timer.interval Description: Specifies the interval, in milliseconds, in which the parse errors are counted per a reliable connection. 0 and below indicates the parse errors are counted globally per the reliable connection. If the interval is running out of time, then the number of parse errors, per the reliable connection, is initialized. Data Type: String Default: 0 CP name: max.content.length Description: Specifies the maximum content-length, in bytes, for a message's body. Data Type: String Default: 65536 (64 Kbytes) The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.9. 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
PI52121
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-11-10
Closed date
2016-03-07
Last modified date
2016-03-07
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
Document Information
Modified date:
28 April 2022