IBM Support

PM14495: A JAX-RPC application sends a soapenc:Array to a web service hosted on a non-IBM application server, which causes a failure.

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 application sends a soap message containing a
    soapenc:Array to a web service hosted on a non-IBM application
    server.  The target web service may fail with an error that
    indicates that that the incoming message could not be processed.
    
    Here is an example message sent from the JAX-RPC web service:
    
    <soapenv:Envelope ..>
    <soapenv:Body>
    <p:method xmlns:p="http://sample.org/">
    <anyType xsi:type="soapenc:Array"
    soapenc:arrayType="xsd:string">
    <item xmlns="">Hello</item>
    <item xmlns="">World</item>
    </anyType>
    </p:mehod>
    </soapenv:Body>
    </p:soapenv:Envelope>
    
    This is a rare scenario.  All of the following conditions must
    be met:
      * The user must be on a fixpack containing PK80836
      * The application must be setting a java.lang.String[] object
        on a parameter or JAX-RPC bean field mapped to
        an xsd:any element.  This is uncommon.
      * The remote web service receiving the message must
        be hosted on a non-IBM application server. The
        WebSphere Application Server will properly receive the
        message.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server users of   *
    *                  JAX-RPC                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: A JAX-RPC application sends a           *
    *                      soapenc:Array in a message.  The        *
    *                      message is rejected by the remote web   *
    *                      service.                                *
    ****************************************************************
    * RECOMMENDATION:  Install a fixpack containing this APAR and  *
    *                  set the following JVM property to true:     *
    *                  com.ibm.websphere.jaxrpc.stub.map.string.arr*
    *                  ay.to.soapenc.array                         *
    ****************************************************************
    A JAX-RPC application sends a soap message containing a
    soapenc:Array to a web service hosted on a non-IBM application
    server.  The target web service may fail with an error that
    indicates that that the incoming message could not be processed.
    
    Here is an example message sent from the JAX-RPC web service:
    
    <soapenv:Envelope ..>
    <soapenv:Body>
    <p:method xmlns:p="http://sample.org/">
    <anyType xsi:type="soapenc:Array"
    soapenc:arrayType="xsd:string">
    <item xmlns="">Hello</item>
    <item xmlns="">World</item>
    </anyType>
    </p:mehod>
    </soapenv:Body>
    </p:soapenv:Envelope>
    
    This is a rare scenario.  All of the following conditions must
    be met:
      * The user must be on a fixpack containing PK80836
      * The application must be setting a java.lang.String[] object
        on a parameter or JAX-RPC bean field mapped to
        an xsd:any element.  This is uncommon.
      * The remote web service receiving the message must
        be hosted on a non-IBM application server. The
        WebSphere Application Server will properly receive the
        message.
    

Problem conclusion

  • APAR PK80836 changed the JAX-RPC runtime such that String[]
    objects are mapped to soapenc:Array schema elements in the
    scenario described in the Problem Description.  The change to
    the java mapping caused the error reported by this APAR.
    
    The JAX-RPC runtime is changed to revert the mapping to the
    algorithm used prior to the PK80836 fix.  This corrects the
    problem reported by APAR PM14495.
    
    In APAR PK80836, the reported problem involved a JAX-RPC
    client application invoking two different web services.  These
    two web services caused the mappings to change within the
    single JAX-RPC TypeMappingRegistry.  If you encounter this
    problem, you should do ONE of the following:
    * Set the following JVM custom property to true:
    com.ibm.websphere.jaxrpc.stub.typemapping.per.thread
    The JVM property is added by APAR PM19223.  Please
    read APAR PM19223 for additional details.
    
    * Set the following JVM custom to true:
    com.ibm.websphere.jaxrpc.stub.map.string.array.to.soapenc.array
    The JVM property is added by this APAR and will map
    a String[] object to a soapenc:Array.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.45 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

    PM14495

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    60W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-13

  • Closed date

    2010-08-30

  • Last modified date

    2010-08-30

  • 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

  • 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

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

Document Information

Modified date:
24 October 2021