PK79942: CLIENT SIDE MUST UNDERSTAND PROCESSING IS NOT CONSIDERING JAXWS HANDLERS.

Fixes are available

APAR status

Closed as program error.

Error description

Must understand processing is not considering JAX-WS handlers if
JAX-WS handlers are configured on the Web Services client.
.
You might see this exception in WebSphere logs:
.
org.apache.axis2.AxisFault: Must Understand check failed s :
{http://someURI}SomeCustomHandler
at
org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngin
e.java:153)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:310)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutIn
AxisOperation.java:399)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(Ou
tInAxisOperation.java:304)
at
org.apache.axis2.jaxws.core.controller.AxisInvocationController.
execute(AxisInvocationController.java:591)
at
org.apache.axis2.jaxws.core.controller.AxisInvocationController.
doInvoke(AxisInvocationController.java:111)
at
org.apache.axis2.jaxws.core.controller.InvocationController.invo
ke(InvocationController.java:110)
at

Local fix

```
N/A.
```

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server users of JAX-WS*
*                  Web Services                                *
****************************************************************
* PROBLEM DESCRIPTION: JAX-WS client receiving response        *
*                      messages containing mustUnderstand="1"  *
*                      SOAP headers are rejected as not        *
*                      understood                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A JAX-WS client can configure JAX-WS application handlers
which participate in processing SOAP Headers.
The handlers indicate which headers they process via their
getHeaders() method.  The headers from all the JAX-WS
application handlers configured on the port should be
considered "understood" during checking of the SOAP headers
marked as "mustUnderstand".  This check is failing, and the
following error may occur:

org.apache.axis2.AxisFault: Must Understand check failed s :
{http://someURI}SomeCustomHandler
at
org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngin
e.java:153)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:310)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutIn
AxisOperation.java:399)

Problem conclusion

The list of headers from the getHeaders() method of the JAX-WS
application handlers configured on a port are now considered
"understood" when the SOAP headers marked "mustUnderstand" on
the inbound response message are checked.


The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.25 and 7.0.0.5.  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
PK79942
Reported component name
WEBSERVIC FEATU
Reported component ID
5724J0850
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-02-03
Closed date
2009-02-26
Last modified date
2009-04-03

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
WEBSERVIC FEATU
Fixed component ID
5724J0850

Applicable component levels

R610 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:
28 December 2021

Tips

PK79942: CLIENT SIDE MUST UNDERSTAND PROCESSING IS NOT CONSIDERING JAXWS HANDLERS.

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

R610 PSY

Document Information

Share your feedback

Need support?