PK73069: STATIC CONTENT INVALIDATED AT THE APPSERVER GETS CACHED AT PROXY SERVER SO CUSTOMERS SEE OLD CONTENT.

Fixes are available

APAR status

Closed as program error.

Error description

IBM WebSphere Applicaiton Server V6.0 and V6.1 Network
Deployment - All operating systems

If static content gets invalidated at the Application
Server, the Proxy Server gets an invalidation message but the
content is still cached by the Proxy Server.

The problem is that the cacheID of the invalidation message
does not match the ID of the cache.

Local fix

The Local Fix:
When IBM WebSphere Application Server is used to serve static
data such as images and HTML on the Application Server, the URLs
are also cached in the ESI processor.  The timeout on this cache
is 300 seconds.  This value can be lowered to invalidate the
cache sooner and help prevent users from seeing old content.

The following example shows how to set a one minute timeout on
static data cached in the plugin:
-Dcom.ibm.servlet.file.esi.timeOut=60

For more information on Edge Side Include caching:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?
topic=/com.ibm.websphere.express.doc/info/exp/ae/tdyn_esiedgecac
hing.html


The fix will involve setting a custom property that will always
force the surrogate-control header from Dynacache to be set on
the response.

In this case the ESI Processor is the WebSphere Proxy which
caches content based on the surrogate-control header set by
WebSphere.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.1 and v7 that are Edge Side Include      *
*                  (ESI) caching static content in the         *
*                  WebSphere Proxy Server or the WebSphere     *
*                  plugin.                                     *
****************************************************************
* PROBLEM DESCRIPTION: Stale ESI cached content in the         *
*                      WebSphere Proxy Server  or the          *
*                      WebSphere Plugin.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If static content gets invalidated at the Application
Server, the Proxy Server gets an invalidation message; however
the ESI cached content is still cached by the Proxy Server.

Problem conclusion

When IBM WebSphere Application Server is used to serve and
cache static data such as images and HTML on the Application
Server, these pages  can be cached in a ESI processor like
the WebSphere Proxy or the Plugin as well. The timeout on this
ESI static cache is 300 seconds. This value can be lowered to
invalidate the cache sooner and help prevent users from seeing
old content. When this static content at application server is
invalidated the content in the ESI cache at the edge is not
removed.

For more information on Edge Side Include caching:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?
topic=/com.ibm.websphere.express.doc/info/exp/ae/tdyn_esiedgecac
hing.html

The fix will involve setting a JVM custom property
Name:com.ibm.ws.cache.CacheConfig.alwaysSetSurrogateControlHdr
Value: true or false
Default value: false

Setting this custom property to "true", will force
the surrogate-control header from Dynacache to be always set on
the response. The surrogate-control header value
contains the metadata needed by the ESI Processor to
correctly generate and invalidate the cached content in the
ESI cache.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.23 and 7.0.0.3.  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
PK73069
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
2008-10-01
Closed date
2008-12-18
Last modified date
2008-12-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

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

Document Information

Modified date:
29 December 2021

Tips

PK73069: STATIC CONTENT INVALIDATED AT THE APPSERVER GETS CACHED AT PROXY SERVER SO CUSTOMERS SEE OLD CONTENT.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?