2
Oracle Application Server Web Cache Error Messages
This chapter describes the error messages, their causes, and suggested actions, that you may encounter when using OracleAS Web Cache, or even after you disable the use of OracleAS Web Cache.
This chapter contains the following OracleAS Web Cache error messages:
Error: Could not open Web cache connection. (WWC-40019)
Cause: This error message is shown in the browser when the invalidation fails. In this case OracleAS Portal was not able to send the invalidation message to OracleAS Web Cache. This happens when the use of OracleAS Web Cache is enabled in OracleAS Portal and any of the following also happen either alone, or together:
- OracleAS Web Cache might not be running. It might have been stopped purposefully in a conscious effort to front-end with the Oracle HTTP Server, instead of OracleAS Web Cache. OracleAS Web Cache might have crashed, or it could have been bounced at the time when the invalidation messages were sent from OracleAS Portal or Providers.
- The OracleAS Web Cache invalidation port could have problems, this can happen because the OracleAS Web Cache invalidation port value in OracleAS Portal is different from the actual OracleAS Web Cache invalidation port. The invalidation port value supplied to the portal using the "-cport_i" parameter during installation could also have been wrong, or the OracleAS Web Cache invalidation port was changed in OracleAS Web Cache after the OracleAS Portal install.
- Some other process grabs the OracleAS Web Cache invalidation port before OracleAS Web Cache can listen on it.
- Trouble with OracleAS Web Cache invalidation password, perhaps because the OracleAS Web Cache invalidator password value in the Portal is different from the actual OracleAS Web Cache invalidator password, or because the invalidator password value supplied to OracleAS Portal using the "-wc_inv_pwd" parameter during the installation was wrong.
- Some security setting in OracleAS Web Cache could have been enabled which might require the OracleAS Web Cache administrator password, instead of the invalidator password.
- Trouble with OracleAS Web Cache hostname because the OracleAS Web Cache hostname value in the Portal is different from the actual OracleAS Web Cache hostname, or the hostname value supplied to the portal using the "-host" and "-chost" parameter during the install could have been wrong.
- OracleAS Web Cache might have been moved to a different Server after the Portal Install, leaving the host on which OracleAS Web Cache runs inaccessible from OracleAS Portal.
- The hostname specified may not include the entire domain name.
- Oracle Application Server Web Cache is not fully disabled. OracleAS Portal can work even without OracleAS Web Cache front-ending the middle-tier. To do this, the "enable_wc_caching" flag in OracleAS Portal should be turned "Off" in addition to shutting down the Oracle Application Server Web Cache. If this is not done any operation which attempts to send an invalidation message will fail with exceptions like "Portal Web Cache settings is On while Web Cache may be down".
Action: Check whether any of the above cases are causing this behavior.
Error: "No Response from Application Server" displays in the browser
Cause: The Oracle HTTP Server might be down.
Action: Check if the Oracle HTTP Server needs to be started.
WWC-40018 - General invalidation message processing exception: %1
Cause: One of the following has happened: 1. An error occurred while sending an invalidation message. This can typically happen when OracleAS Web Cache goes down or is stopped while OracleAS Portal is writing an invalidation message to the OracleAS Web Cache invalidation port. 2. Some other unexpected exception occurred while processing an invalidation message.
Action: Ensure that OracleAS Web Cache is running and the invalidation port is accepting connections.
