IBM Support

PI80922: ISSUES WITH RESPONSEWRAPPER AFTER PI60666

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Changes made in PI60666 added code to include all JAX-WS
    artifacts in classpath, which includes the RequestWrapper and
    ResponseWrapper classes.
    
    This can cause regression in certain applications. If the
    ResponseWrapper class is the same for multiple services, there
    is no way to differentiate them. The first class found is used
    for marshalling the response.
    
    This APAR implements a new custom property,
    com.ibm.ws.websvcs.DisableIncludeAllCachePaths, which restores
    the previous behavior when set to "true".
    

Local fix

  • Update the application to avoid using the same canonical class
    name for all ResponseWrapper, or don't use the ResponseWrapper
    so that the default class name will be used.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server for JAX-WS Web services.             *
    ****************************************************************
    * PROBLEM DESCRIPTION: After upgrading to WAS 8.5.5.11,        *
    *                      client may receive incorrect SOAP       *
    *                      response.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The different result is related to the changes made in
    PI60666, which would add all JAX-WS artifacts in classpath,
    including the RequestWrapper and ResponseWrapper classes.
    This could cause unexpected results in some applications where
    multiple services share the same ResponseWrapper class name.
    Since JAX-WS runtime cannot differentiate these
    ResponseWrapper classes, the first class found is used for
    marshalling the response.
    

Problem conclusion

  • This APAR implements a new custom property,
    com.ibm.ws.websvcs.DisableIncludeAllCachePaths, which restores
    the previous behavior when it's set to "true".
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.12 and 9.0.0.5.  Please refer to the Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=sw
    g27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI80922

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-05-02

  • Closed date

    2017-06-26

  • Last modified date

    2017-10-19

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
06 September 2021