PK97682: JAX-WS THROWS SOAPFAULTEXCEPTION INSTEAD OF EXPECTED APPLICATION EXCEPTION

Fixes are available

APAR status

Closed as program error.

Error description

A JAX-WS proxy throws a SOAPFaultException instead of the
expected application exception.

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of JAX-WS                                   *
****************************************************************
* PROBLEM DESCRIPTION: The JAX-WS proxy throws a               *
*                      SOAPException instead of an             *
*                      application exception                   *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
When an inbound SOAP message contains a SOAP Fault, the JAX-WS
proxy will throw either a system exception or a service
exception.

Sometimes a service exception is referred to as an
application exception because it is an exception defined by
the application.  If a system exception is thrown, the
exception is usually a javax.xml.ws.soap.SOAPFaultException.

In some cases, a non-IBM vendor will add additional elements
into detail section of the SOAP Fault message.  Here is an
example:

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<S:Fault>
<faultcode>S:Server</faultcode>
<faultstring>Application Exception</faultstring>
<detail>
<usr:appException xmlns:usr="http://sample">
user data
</usr:appException>
<stacktrace>
debug data
</stacktrace>
</detail>
</S:Fault>
</S:Envelope>

In the message above, the JAX-WS engine should use the
"appException" element to throw a service exception.  However,
the presence of the "stacktrace" element causes the JAX-WS
engine to incorrectly throw a SOAPFaultException.

Problem conclusion

The elements inside a detail element are referred to as detail
entries.  The JAX-WS engine is changed to use the first detail
entry to find and throw a service exception.

The fix for this APAR is currently targeted for inclusion in
fix pack 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
PK97682
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-01
Closed date
2009-10-17
Last modified date
2009-10-17

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
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"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:
24 October 2021

Tips

PK97682: JAX-WS THROWS SOAPFAULTEXCEPTION INSTEAD OF EXPECTED APPLICATION EXCEPTION

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

Document Information

Share your feedback

Need support?