Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B15849-03 |
|
Previous |
Next |
This chapter describes the issues associated with Oracle Application Server Web Cache (OracleAS Web Cache). It includes the following topics:
This section describes configuration issues and their workarounds for OracleAS Web Cache. It includes the following topics:
Section 8.1.1, "Reloading Issue with Cache Operations Success Message in Internet Explorer Browser"
Section 8.1.4, "Failure to Invalidate Content in Configurations with Uppercase Site Host Names"
When you submit a successful operation in the Cache Operations page (Cache Operations in Operations) in OracleAS Web Cache Manager, a success dialog 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 dialog box itself.
The Global URL Parameters to Ignore dialog box is displayed when you select Edit Global URL Parameters to Ignore from the Site Definitions page of 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.To workaround this behavior, navigate to the Web Cache Home page, select the Administration tab, Properties, Application, Sites, and then Oracle Enterprise Manager Application Server Control. Select the Global URL Parameters option in the Defaults and Global Settings section to configure parameters to exclude.
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, then OracleAS Web Cache correctly recognizes the node failure. However, invalidation requests are still sent to the shutdown node as part of invalidation propagation, resulting in a timeout of 300 seconds for those requests. A message similar to the following is reported in 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 Oracle Application Server Web Cache Administrator's Guide |
In Oracle Application Server 10g Release 2 (10.1.2), advanced invalidation requests fail for 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 Console. To access the Sites page, navigate to the Web Cache Home page. On the Administration tab, select Properties, Applications, and then Sites. You can also specify the site configuration on the Site Definitions page of OracleAS Web Cache Manager. To access this page, navigate to Origin Servers, Sites, and Load Balancing, and then select Site Definitions.
This section describes the documentation errata.
Section "Listing Popular Requests and Cache Contents" in Chapter 15, "Using Diagnostics Tools", in 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. The output for popular requests also includes cached but expired objects.