Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux PA-RISC (64-bit)
B15511-05
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

15 Oracle Application Server Web Cache

This chapter describes the issues associated with Oracle Application Server Web Cache (OracleAS Web Cache). It includes the following topics:

15.1 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds for OracleAS Web Cache. It includes the following topics:

15.1.1 Reloading Issue with Cache Operations Success Message in OracleAS Web Cache Manager with Internet Explorer Browser

When you submit a successful operation in the Cache Operations page (Operations > Cache Operations) in OracleAS Web Cache Manager, a Success message box appears. When you click OK to acknowledge the message, on versions of Internet Explorer running on Macintosh, the Success dialog box reloads the OracleAS Web Cache Manager interface into the message box itself.

15.1.2 Failure When Submitting Global URL Parameters to Ignore in OracleAS Web Cache Manager

In some cases, when you submit parameters to ignore in the Global URL Parameters to Ignore dialog box of OracleAS Web Cache Manager, the submission is ignored and the Global URL Parameters to Ignore dialog box continues to display. You access the Global URL Parameters to Ignore dialog box when you select Edit Global URL Parameters to Ignore from the Site Definitions page of OracleAS Web Cache Manager (Origin Servers, Sites, and Load Balancing > Site Definitions).

To workaround this behavior, navigate to the Sites page of Oracle Enterprise Manager Application Server Control (Web Cache Home page > Administration tab > Properties > Application > Sites), and select the Global URL Parameters option in the Defaults and Global Settings section to configure parameters to exclude.

15.1.3 Invalidation Timeout Issue During Invalidation Propagation to a Cache Cluster Member

Invalidation has a default timeout of 300 seconds for the propagation of invalidation requests. If a node is not running and is configured as a cache cluster member in a cache cluster, OracleAS Web Cache correctly recognizes the node failure. However, invalidation requests are still sent to the shutdown node as a part of a invalidation propagation, resulting in a 300-second timeout for those requests. A message similar to the following is reported in the response to the invalidation request:

Can't connect to the web cache's invalidation listening port.

To avoid the long timeout, remove the cache cluster member from the cluster.


See Also:

Section "Removing Caches from a Cluster" in Chapter 10, "Configuring Cache Clusters," in the Oracle Application Server Web Cache Administrator's Guide

15.1.4 Failure to Invalidate Content in Configurations with Uppercase Site Host Names

In 10g Release 2 (10.1.2), advanced invalidation requests fail in configurations that specify an uppercase or mixed case host name in the site definition for the site itself or any of its aliases. For example, you specify WWW.COMPANY.COM or WWW.Company.COM instead of www.company.com in the site definition.

To workaround this issue, change the host name value used in the sites and site aliases configuration to lowercase. For example, change WWW.COMPANY.COM to www.company.com. You specify the site configuration in the Sites page of Application Server Control (Web Cache Home page > Administration tab > Properties > Application > Sites) or the Site Definitions page of OracleAS Web Cache Manager (Origin Servers, Sites, and Load Balancing > Site Definitions).

15.2 Documentation Errata

This section describes documentation errata. It includes the following topic:

15.2.1 Incorrect Note in Oracle Application Server Web Cache Administrator's Guide

Section "Listing Popular Requests and Cache Contents" in Chapter 15, "Using Diagnostics Tools," in the Oracle Application Server Web Cache Administrator's Guide contains the following note:


Note:

OracleAS Web Cache Manager lists only those objects that are valid. Although the cache may contain objects that are expired or that have been invalidated, those objects are not included in these lists.

Disregard this note. Output for popular requests also includes cached but expired objects.