PK92275: A JAX-RPC WEB-SERVICE WITH A DYNACACHE HANDLER RETURNS AN UNEXPECTED RESPONSE.

Fixes are available

APAR status

Closed as program error.

Error description

The Dynamic Cache Service is configured to do JAX-RPC Client
caching for a particular web service call. The first web
service call works correctly, and a cache miss is seen in the
monitor.

Subsequent calls to the web service result in a cache hit as is
expected, but the JAX-RPC application handlers are not being
invoked on the response path, causing an unexpected response
to be returned to the client.

Local fix

```
NA
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  Dynamic Cache Service in conjunction with   *
*                  JAX-RPC application handlers.               *
****************************************************************
* PROBLEM DESCRIPTION: JAX-RPC application handlers are not    *
*                      called in handleResponse after a        *
*                      Dynamnic Cache Service hit.             *
****************************************************************
* RECOMMENDATION:  Install a fix pack that includes this APAR. *
****************************************************************
When Dynamic Cache Service is enabled, the DynaCache Handler
is inserted into the handler chains for the JAX-RPC
web service flow. When the DynaCache Handler is invoked in
its handleRequest method, it will look for a cache hit.  If a
hit is found, it will correctly populate the response message
and return the value "false" from handleRequest.

The JAX-RPC web service runtime was detecting the
"false" return value but it was not invoking handleResponse
on all of the JAX-RPC application handlers in the chain.

In this case the failure to call handleResponse resulted in an
incorrect response being returned to the client.

According to the JAXRPC-1.1 spec (section 12.2.2)
The handleRequest method performs one of the following steps
after performing
handler specific processing of the request SOAP message:
....
? Return false to indicate blocking of the request handler
chain. In this case, further processing of the request handler
chain is blocked and the target service endpoint is not
dispatched. The JAX-RPC runtime system takes the
responsibility of invoking the response handler chain next with
the appropriate SOAPMessageContext. The Handler implementation
class has the responsibility of setting the response SOAP
message in the handleRequest method and perform additional
processing in the handleResponse method. In the default
processing model, the response handlerchain starts processing
from the same Handler instance (that returned false) and goes
backward in the execution sequence.

Problem conclusion

The JAX-RPC Handler runtime has been updated so that upon
detecting a false return value from handleRequest, it will
invoke handleResponse on all handlers which had previously been
invoked in handleRequest.

The fix for this APAR is currently targeted for inclusion in
fix pack 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
PK92275
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-24
Closed date
2009-09-01
Last modified date
2009-09-01

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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK92275: A JAX-RPC WEB-SERVICE WITH A DYNACACHE HANDLER RETURNS AN UNEXPECTED RESPONSE.

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?