IBM Support

PM16191: WEB SERVICES CACHE CANNOT BE DISABLED FOR JAX-WS APPLICATION RETURNING A SOAPFAULT RESPONSE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a JAX-WS client application sends a request that will
    result in an anticipated SOAPFault being returned, as per
    application logic, the Web services cache component caches the
    response for this request.
    
    However, the web services runtime should not enable caching of
    SOAPFault responses (the request should not produce a cache
    hit).
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Feature Pack for Web Services JAW-WS *
    *                  client applications and Web service         *
    *                  response caching                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Web service SOAPFault responses are     *
    *                      being cached                            *
    ****************************************************************
    * RECOMMENDATION:  Install a fixpack that contains this APAR   *
    ****************************************************************
    The JAX-WS Web service runtime is permitting
    SOAPFault responses, generated in response to JAX-WS client
    requests, to be cached by the Web services cache component.
    
    However, responses containing a SOAPFault should not be
    cached. Since the SOAPFault may be generated due to a condition
    being met in the application logic, and the condition may no
    longer apply, there exists a possibility for the cached
    SOAPFault response to return when a normal response is supposed
    to be returned.
    

Problem conclusion

  • The JAX-WS runtime has been corrected to disable Web
    service caching in the instance that a request results in a
    SOAP response containing a SOAPFault.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.33. This same problem is resolved by PM16481
    for IBM WebSphere Application Server v7
    
    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

    PM16191

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-06-09

  • Closed date

    2010-06-24

  • Last modified date

    2010-10-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM16481

Fix information

  • Fixed component name

    WEBSERVIC FEATU

  • Fixed component ID

    5724J0850

Applicable component levels

  • R610 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022