PM22424: A JAX-RPC Web service sends a message contain a SOAP Fault, which may not inter-operate with old versions of .NET

Fixes are available

APAR status

Closed as program error.

Error description

A JAX-RPC Web service on WebSphere Application Server V5.1 may
respond with a SOAP Fault, which uses a default namespace to
define the contents of the Fault detail.

Here is an example message from WebSphere Application Server
Version 5.1:

<soapenv:Fault
xmlns:soapenv=
"http://schemas.xmlsoap.org/soap/envelope/">
<faultcode xmlns="http://sample">
sampleFault
</faultcode>
<faultstring>sample text</faultstring>
<detail encodingStyle="">
<sampleFault
xmlns="http://sample">
...
</sampleFault>
</detail>
<soapenv:Fault>

A JAX-RPC Web service on WebSphere Application Server V6.0 or
higher may respond with a SOAP Fault, which uses an actual
prefix name to locate the namespace.

Here is an example message from WebSphere Application Server
Version 6.0:

<soapenv:Fault
xmlns:soapenv=
"http://schemas.xmlsoap.org/soap/envelope/">
<faultcode xmlns:p123="http://sample">
p123:sampleFault
</faultcode>
<faultstring>sample text</faultstring>
<detail encodingStyle="">
<p123:sampleFault
xmlns:p123="http://sample">
...
</p123:sampleFault>
</detail>
<soapenv:Fault>


Both of these messages are legal and valid.
Both of these messages are correctly processed by an IBM
client that is a WebSphere Application Server.

However some older versions of Microsoft .NET are not compliant
with the XML Schema Specification.  If a Microsoft .NET client
receives the message sent from the V6.0 WebSphere Application
Server, it may fail.

Local fix

```
na
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
*                  V7.0 administrators of JAX-RPC Web          *
*                  Services                                    *
*                  interacting with older Microsoft .NET       *
*                  clients                                     *
****************************************************************
* PROBLEM DESCRIPTION: A JAX-RPC Web service sends a message   *
*                      containing a SOAP Fault, which may not  *
*                      inter-operate with old versions of      *
*                      Microsoft .NET                          *
****************************************************************
* RECOMMENDATION:  Install a fix pack containing this APAR     *
*                  and                                         *
*                  set the new JVM property:                   *
*                  com.ibm.ws.webservices.serializeDetailEleme *
*                  n                                           *
*                  tUsingDefaultNamespace=true                 *
****************************************************************
A JAX-RPC Web service on WebSphere Application Server V5.1 may
respond with a SOAP Fault, which uses a default namespace to
define the contents of the Fault detail.
Here is an example message from WebSphere Application Server
Version 5.1:
<soapenv:Fault
xmlns:soapenv=
"http://schemas.xmlsoap.org/soap/envelope/">
<faultcode xmlns="http://sample">
sampleFault
</faultcode>
<faultstring>sample text</faultstring>
<detail encodingStyle="">
<sampleFault
xmlns="http://sample">
...
</sampleFault>
</detail>
<soapenv:Fault>
A JAX-RPC Web service on WebSphere Application Server V6.0 or
higher may respond with a SOAP Fault, which uses an actual
prefix name to locate the namespace.
Here is an example message from WebSphere Application Server
Version 6.0:
<soapenv:Fault
xmlns:soapenv=
"http://schemas.xmlsoap.org/soap/envelope/">
<faultcode xmlns:p123="http://sample">
p123:sampleFault
</faultcode>
<faultstring>sample text</faultstring>
<detail encodingStyle="">
<p123:sampleFault
xmlns:p123="http://sample">
...
</p123:sampleFault>
</detail>
<soapenv:Fault>
Both of these messages are legal and valid.
Both of these messages are correctly processed by an IBM
client that is a WebSphere Application Server.
However some older versions of Microsoft .NET are not compliant
with the XML Schema Specification.  If a Microsoft .NET client
receives the message sent from the V6.0 WebSphere Application
Server, it may fail.
This problem may occur when an administrator migrates a
JAX-RPC application from V5.1 to V6.0.  In such cases, the
administrator may not be able to upgrade or change all of the
Microsoft .NET clients.

Problem conclusion

A JVM property is added to the JAX-RPC runtime.

Property Name:
com.ibm.ws.webservices.serializeDetailElementUsingDef
aultNamespace
Values:
true or false
Default Value:
false
Description:
When this property is set to true, the contents of the
detail element will be defined using a default namespace.
Thus the message will be similar to the message sent from a V5.0
WebSphere Application Server.

You should also set the following similar property, which was
added by APAR PK66483:
com.ibm.ws.webservices.serializeOperationElementUsingDef
aultNamespace=true

The following link provides information on how to set JVM
properties:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?
topic=/com.ibm.websphere.express.doc/info/exp/ae/xrun_jvm.html

The following property is specific to JAX-RPC only. In JAX WS,
for performance reasons and canonicalization, default
namespaces are discouraged. A possible alternative would be to
intercept the message with a SOAP handler and manipulate the
element so that it's marshalled with a default
namespace.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.35 and 7.0.0.15.  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
PM22424
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61S
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-09-14
Closed date
2010-09-27
Last modified date
2012-04-18

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":"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

PM22424: A JAX-RPC Web service sends a message contain a SOAP Fault, which may not inter-operate with old versions of .NET

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?