PK68260: CLIENT JAX-RPC HANDLER'S HANDLEFAULT() BEING INVOKED IN A ONE-WAY OPERATION.

Fixes are available

APAR status

Closed as program error.

Error description

During a One-Way operation mode,  when an exception occurs, the
customer observed that the handleFault() of the exit
handler code is being invoked which should "never" be the case.

As per the JAX-RPC 1.1, section 12.1.4 "HandlerChain"

"In the case of a one-way call, only the handleRequest methods
are invoked. Neither handleResponse nor handleFault methods are
invoked as part of the processing of the SOAP message
HandlerChain."

It was noticed that the client's handler's handleFault() was
being invoked. The Webservice engine was not detecting the
operation as one-way and thus resulting in the above behaviour
wherein a Fault is being returned.

The APAR corrects the above problem and ensures that the
handleFault() does not get invoked for a One-Way operation
within the client's handler code.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6 invoking web service one-way operations  *
*                  and implementing JAX-RPC handlers           *
****************************************************************
* PROBLEM DESCRIPTION: A client calls a one-way operation,     *
*                      but its JAX-RPC handler's               *
*                      handleFault() method is invoked,        *
*                      which is a JAX-RPC violation.           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A JAX-RPC client calls a one-way operation. It also contains
a JAX-RPC handler, which implements the
javax.xml.rpc.handler.Handler.handleFault() method. The
servlet URI given in the endpoint URL is unavailable, so the
server returns an HTTP code 404 Not Found. When the web services
engine detects this error, it incorrectly invokes the
client handler's handleFault() method, which is a violation of
JAX-RPC 1.1 section 12.1.4 "HandlerChain."

Problem conclusion

The web services engine was changed so it will not invoke the
client handler's handleFault() method when the server
returns an HTTP error code.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.0.2.33 and 6.1.0.21.  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
PK68260
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-06-26
Closed date
2008-09-08
Last modified date
2008-09-08

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

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

Document Information

Modified date:
29 December 2021

Tips

PK68260: CLIENT JAX-RPC HANDLER'S HANDLEFAULT() BEING INVOKED IN A ONE-WAY OPERATION.

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

Document Information

Share your feedback

Need support?