IBM Support

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

6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

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



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM22424

Modified date: 18 April 2012