IBM Support

PM57278: PROXY DOES NOT CHECK FOR INVALID CACHE ENTRY.

Fixes are available

7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
PM57278: Proxy server responds with partial responses or just response headers
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

  • WebSphere Application Server Proxy will call Dynacache for
    a cached entry and does not check for valid segments.  The
    following exception is thrown:
    
    [1/26/12 15:58:51:169 CET] 00000056 HttpProxyConn 3
    auditException:
    service context=HttpProxyServiceContextImpl@1dde1dde, connection
    link=HttpProxyConnectionLink@1dce1dce, source=INBOUND,
    reporter=com.ibm.ws.proxy.channel.http.HttpInboundWriteCallback@
    40c540c5
    ,
    t=com.ibm.wsspi.http.channel.exception.HttpInvalidMessageExcepti
    on:
    Response length: 60245 0detailFlag=0
    

Local fix

  • The disk caching can be enabled from the admin panels by
    navigating to
    the "Proxy Cache instance config" which is under the "HTTP Proxy
    Server
    Setting" tab on the main proxy panel.  From that panel, select
    the Proxy
    Cache Store to change the settings.  Check the "Enable disk
    offload"
    checkbox.  This will expand the disk settings.  The defaults
    should be
    sufficient.
    
    Enabling the disk cache will prevent the problem from occurring
    because
    when the memory cache becomes full the entry selected for
    eviction is
    moved to disk rather than invalidated.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 and V8.0 Proxy Server           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Proxy server responds with partial      *
    *                      responses or just response headers      *
    *                      when a cached segment has been          *
    *                      invalidated from cache.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the proxy server is serving a response from the cache and
    a segment of that cached object has been invalidated from the
    cache by dynacache, then the proxy server will be unable to
    send any or part of the response body back to the client.  It
    could send part of the response body or just the HTTP response
    headers. All request for that cached object will fail until
    the entire object is removed from the cache. The Proxy would
    issue the following audit exception trace similar to this:
    [1/26/12 15:58:51:169 CET] 00000056 HttpProxyConn 3
    auditException: service
    context=HttpProxyServiceContextImpl@1dde1dde, connection
    link=HttpProxyConnectionLink@1dce1dce, source=INBOUND,
    reporter=com.ibm.ws.proxy.channel.http.HttpInboundWriteCallback@
    40c540c5,
    t=com.ibm.wsspi.http.channel.exception.HttpInvalidMessageExcepti
    on: Response length: 60245 0detailFlag=0
    

Problem conclusion

  • The proxy server code has been changed to remove the cached
    item when it detects that any part of the cached object is no
    longer in the cache.
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.23 and 8.0.0.4.  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

    PM57278

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-02

  • Closed date

    2012-02-23

  • Last modified date

    2012-07-03

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM57278

Modified date: 03 July 2012