PM05787: A cookie without attributes may be missing for JAX-RPC SOAP requests.

Fixes are available

APAR status

Closed as program error.

Error description

For JAX-RPC applications, all cookies should be included in
the HTTP headers of the Web services SOAP requests.  Following
is an example HTTP header list which includes a cookie:

POST /IBMWebServiceRouter/services/IBMQueryPort HTTP/1.1
Host: x.x.x.x:port_number
Accept: application/soap+xml,multipart/related,text/*
User-Agent: IBM WebServices/1.0
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Cookie: $Version="1";LtpaToken2=<token_data_removed>
Connection: Keep-Alive
Content-Type: text/xml; charset=utf-8
Content-Length: 433
Date: Tue, 19 Jan 2010 19:44:23 GMT
<SOAP request message>

There are cases where a cookie without attributes may be
missing from the HTTP header of SOAP request.
Following is an example of HTTP header list where a
cookie is missing:

POST /IBMWebServiceRouter/services/IBMQueryPort HTTP/1.1
Host: x.x.x.x:port_number
Accept: application/soap+xml,multipart/related,text/*
User-Agent: IBM WebServices/1.0
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Cookie: $Version="1"
Connection: Keep-Alive
Content-Type: text/xml; charset=utf-8
Content-Length: 433
Date: Tue, 19 Jan 2010 19:13:55 GMT
<SOAP request message>

An example of a cookie that may not have attributes is an
LtpaToken2 token.  When a LtpaToken2 is missing from the
HTTP header, a "(401) Unauthorized" error may occur.

Local fix

Use WebSphere Application Server FixPack v7.0.0.5 instead of
v7.0.0.7

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  JAX-RPC applications utilizing HTTP         *
*                  cookies.                                    *
****************************************************************
* PROBLEM DESCRIPTION: Cookies that do not have attributes     *
*                      (example:"LtpaToken2=abcdef") may not   *
*                      be set in a JAX-RPC SOAP request.       *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR.     *
****************************************************************
When you set a cookie that does not have attributes
(example:"LtpaToken2=abcdef"), the web services utility
code may not set the cookie name and cookie value in the HTTP
header of the SOAP request.

Problem conclusion

The JAX-RPC web services utility code is corrected to properly
set the cookie name and value in the HTTP header of the
request when a cookie does not have attributes.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.41, 6.1.0.31 and 7.0.0.11.  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
PM05787
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
2010-01-22
Closed date
2010-02-22
Last modified date
2010-02-22

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

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
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

PM05787: A cookie without attributes may be missing for JAX-RPC SOAP requests.

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?