Oracle® Application Server Release Notes 10g Release 2 (10.1.2) for hp-ux Itanium and Linux Itanium B15871-05 |
|
![]() 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 known issues for OracleAS Web Cache. It includes the following topic:
If you start OracleAS Web Cache using the OracleAS Web Cache Manager on SUSE Linux Enterprise Server 9, the following error is displayed:
Error communicating with remote admin server
However, OracleAS Web Cache starts successfully and the error can be safely ignored.
This section describes configuration issues and their workarounds for OracleAS Web Cache. It includes the following topics:
Section 8.2.1, "Reloading Issue with Cache Operations Success Message in Internet Explorer Browser"
Section 8.2.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 appears. When you click OK to acknowledge the message, on versions of Internet Explorer running on Macintosh, the success dialog reloads the OracleAS Web Cache Manager interface into the dialog itself.
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.
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 an invalidation propagation, resulting in a 300-second timeout 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 the 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 (Navigate to the Web Cache Home page. In the Administration tab, Select Properties. Select Applications and then Sites) or the Site Definitions page of OracleAS Web Cache Manager (Origin Servers, Sites, and Load Balancing > Site Definitions).
This section describes the documentation errata.
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. The output for popular requests also includes cached but expired objects.