PK95864: THE SIP (SESSION INITIATION PROTOCOL) CONTAINER FAILS TO PARSE A MESSAGE THAT ARRIVES OVER TCP.

Fixes are available

APAR status

Closed as program error.

Error description

The SIP (Session Initiation Protocol) container receives a
message from the transport layer, over TCP, but when it passes
the message up to the application, the body of the message is
truncated, with the last byte missing from the body.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Session Initiation Protocol (SIP) users of  *
*                  IBM WebSphere Application Server V6.1 and   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: Incorrect parsing of a message that     *
*                      arrives in two packets, and is sliced   *
*                      right between the header and the body.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem happens when sending a message to the container
over a stream transport (either TCP or TLS) and the message
arrives in two network packets, split between the header and
the body. In every SIP message the header section ends with
CR (carriage-return character) followed by LF (line-feed
character). The bug occurs if the message is fragmented in the
network so the first segment ends with the CR and the second
segment starts with the LF. Given this specific fragmentation,
the parser regards the LF as the first byte in the body,
although it does not belong in the message body. Then the
parser goes on to parse the rest of the message body,
according to the expected number of bytes as specified in the
Content-Length header field value. Since the parser counts the
LF as part of the body, it reads the remaining body bytes
until one character before the end of the message, leaving the
last character out. This results in passing a corrupted
message up to the application, and in failure to parse
consecutive messages that are sent over the same connection.

Problem conclusion

The problem is fixed in the SIP (Session Initiation Protocol)
container. With this fix, messages are correctly presented to
the application regardless of network fragmentation.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.29 and 7.0.0.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
PK95864
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-10
Closed date
2009-10-22
Last modified date
2009-11-11

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK95864: THE SIP (SESSION INITIATION PROTOCOL) CONTAINER FAILS TO PARSE A MESSAGE THAT ARRIVES OVER TCP.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?