PM42155: A JAX-WS CLIENT MIGHT INVOKE AN UNEXPECTED WEB SERVICE ENDPOINT DUE TO IMPROPER CACHING OF CONNECTION OBJECTS

Fixes are available

APAR status

Closed as program error.

Error description

A JAX-WS client can programmatically change the endpoint
address URL where its requests are sent.

Problems can occur if the URLs share the same short hostname
and request URI. For example, the client first sends the
request to http://lilygirl:9080/Test/HelloWorld. Then, the
client changes the endpoint address so that the request goes to
http://lilygirl.austin.ibm.com/Test/HelloWorld.

The two URLs are different, but share the same short name of
the host (lilygirl) and the same request URI
(Test/HelloWorld). The JAX-WS runtime might mistakenly treat
the two URLs the same, and therefore might return a previously
cached connection object for the incorrect URL. This can
result in the request going to the wrong endpoint.

Local fix

```
Use disableWSAddressCaching
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application          *
*                  Server JAX-WS clients using the HTTP        *
*                  transport.                                  *
****************************************************************
* PROBLEM DESCRIPTION: A JAX-WS client might invoke an         *
*                      unexpected web service endpoint due     *
*                      to improper caching of connection       *
*                      objects.                                *
****************************************************************
*                  * RECOMMENDATION:  Install a fixpack that inc
****************************************************************
A JAX-WS client can programmatically change the endpoint
address URL where its requests are sent.
Problems can occur if the URLs share the same short hostname
and request URI. For example, the client first sends the
request to http://lilygirl:9080/Test/HelloWorld. Then, the
client changes the endpoint address so that the request goes to
http://lilygirl.austin.ibm.com/Test/HelloWorld.
The two URLs are different, but share the same short name of
the host (lilygirl) and the same request URI
(Test/HelloWorld). The JAX-WS runtime might mistakenly treat
the two URLs the same, and therefore might return a previously
cached connection object for the incorrect URL. This can
result in the request going to the wrong endpoint.

Problem conclusion

The JAX-WS runtime was corrected to properly differentiate
between unique URLs.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.21 and 8.0.0.2.  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
PM42155
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
2011-06-21
Closed date
2011-07-07
Last modified date
2011-07-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

R700 PSY
UP
R800 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:
27 October 2021

Tips

PM42155: A JAX-WS CLIENT MIGHT INVOKE AN UNEXPECTED WEB SERVICE ENDPOINT DUE TO IMPROPER CACHING OF CONNECTION OBJECTS

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

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?