Skip Headers

Oracle Application Server Web Cache Administrator's Guide
10g (9.0.4)

Part Number B10401-01
Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

16
Event Log Messages

This chapter contains a complete listing of the event logs messages, except those with a severity level of debug or internal error. It contains these topics:

Message Format

The prefix "WXE" shows that the message was generated by OracleAS Web Cache. All messages are listed in order by the message code number. To look up a message, use the message code number.

Each message is rated by severity:

In addition, OracleAS Web Cache provides messages, that are not documented in this chapter, with severity levels of debug or internal error:

Messages

WXE-00800 Auto-Restart started successfully

Severity: notification

Cause: The Auto-Restart process has successfully completed its initialization.

Action: No action required.

WXE-08000 Internal error. Auto-Restart process terminating.

Severity: alert

Cause: An internal error occurred in the Auto-Restart process.

Action: This error usually occurs as a result of insufficient system resources. If the problem persists, contact Oracle Support Services.

WXE-08001 Failed to start the cache server. Auto-Restart process terminating.

Severity: alert

Cause: Failed to start the OracleAS Web Cache server.

Action: This error usually occurs as a result of insufficient system resources. If the problem persists, contact Oracle Support Services.

WXE-08002 Failed to find a Web Cache listening port that does not require SSL client-side certificates. Auto-Restart pinging is disabled.

Severity: warning

Cause: Auto-Restart does not support the use of client-side certificates. If all Web Cache listening ports require client-side certificates, then pinging is disabled in the Auto-Restart mechanism.

Action: To enable pinging, add a listening port that does not require client-side certificates.

WXE-08500 Cache server not responding on port %d.

Severity: error

Cause: The cache server may not have been running. The Auto-Restart process will continue to try to reach the cache server on the specified port.

Action: No action required.

WXE-08501 Timeout occurred communicating with the cache server.

Severity: error

Cause: The cache server was either in an unstable state or slow responding to queries.

Action: From the Auto-Restart page of the OracleAS Cache Manager, check the Ping Timeout interval and increase it if necessary.

WXE-08502 Lost connection with the cache server.

Severity: error

Cause: There were communication errors between the Auto-Restart process and the cache server. The Auto-Restart process will continue to try to reach the cache server.

Action: No action required.

WXE-08503 Operating system level error in %s() (%d): %s.

Severity: error

Cause: The specified system call returned the specified error.

Action: No action required.

WXE-08504 %u consecutive errors pinging the cache server.

Severity: notification

Cause: The Auto-Restart process received the specified number of failures when attempting to reach the cache server.

Action: No action required.

WXE-08505 %u consecutive error(s) pinging the cache server. %d error(s) required for restart.

Severity: notification

Cause: The Auto-Restart process received the specified number of failures when attempting to reach the cache server. The error message indicates the number of times the Auto-Restart process will attempt to reach the cache server.

Action: No action required.

WXE-08506 Unable to retrieve the cache server process ID from %s. Stopping the Auto-Restart process.

Severity: alert

Cause: Unable to read the OracleAS Web Cache server pid file. Most likely the file was deleted during a normal termination of the server. As a result, the Auto-Restart process was also shut down.

Action: No action required.

WXE-08507 Cache server process not running.

Severity: notification

Cause: There was no process on the system matching the process ID listed in the OracleAS Web Cache server pid file.

Action: No action required.

WXE-08508 Restarting the cache server.

Severity: alert

Cause: See accompanying error messages for more information.

Action: No action required.

WXE-08509 Starting the cache server.

Severity: alert

Cause: See accompanying error messages for more information.

Action: No action required.

WXE-08510 SSL set hardware acceleration failed. NZERROR=%s.

Severity: error

Cause: The SSL library failed to initialize the hardware SSL acceleration. The specified error message provides more detail.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-08511 SSL Set Thread Usage Failed. NZERROR=%s.

Severity: error

Cause: The SSL library failed to set the threading model. The specified error message provides more detail.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-08512 SSL Engine Failed to Initialize. NZERROR=%s.

Severity: error

Cause: The SSL engine failed to initialize. The specified error message provides more detail.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-09001 An error occurred while disabling core file creation.

Severity: warning

Cause: Internal error. The system/library call to disable core file creation returned an error.

Action: If the problem persists, contact Oracle Support Services.

WXE-09200 An error occurred while trying to create a background process.

Severity: alert

Cause: Could not open standard input while OracleAS Web Cache is creating a process.

Action: Determine why OracleAS Web Cache cannot read standard input or write to standard output for null device.

WXE-09403 Maximum number of file/socket descriptors set to %s.

Severity: notification

Cause: The specified number of file descriptors is set for use by OracleAS Web Cache.

Action: No action required.

WXE-09521 Failed to find User ( %s ) in /etc/passwd.

Severity: alert

Cause: The specified user was not found in the password file.

Action: Add user to the password file.

WXE-09522 Failed to find Group ( %s ) in /etc/group.

Severity: alert

Cause: The specified group was not found in the group file.

Action: Add the group to the group file or modify the group ID in the Process Identity page of OracleAS Web Cache Manager.

WXE-09523 Invalid user ID ( %s ).

Severity: alert

Cause: The specified user ID was invalid.

Action: Correct the user ID in the Process Identity page of OracleAS Web Cache Manager.

WXE-09524 Invalid group ID ( %s ).

Severity: alert

Cause: The specified group ID was invalid.

Action: Correct the group ID in the Process Identity page of OracleAS Web Cache Manager.

WXE-09525 Permission denied when setting user ID ( %s ).

Severity: alert

Cause: The specified user did not have the required permissions when setting the user ID.

Action: Grant the user required permissions or log in as a different user.

WXE-09526 Permission denied when setting group ID ( %s ).

Severity: alert

Cause: The user did not have the required permissions when setting group ID.

Action: Grant the user required permissions or log in as a different user.

WXE-09534 Unexpected File I/O Error ( %s ) when opening file %s.

Severity: alert

Cause: Could not open specified file.

Action: Review specified error to determine the problem on your system.

WXE-09570 Directory not found when unlinking file %s

Severity: notification

Cause: The directory was not found.

Action: Verify that OracleAS Web Cache was installed properly. You may need to reinstall OracleAS Web Cache.

WXE-09571 Too many files open when unlinking file %s.

Severity: notification

Cause: Too many files were open for available system resources.

Action: Adjust system resources and restart OracleAS Web Cache.

WXE-09572 No disk space available when unlinking file %s

Severity: notification

Cause: Insufficient disk space was available on the system.

Action: The system is running low on disk space. Free up disk space and restart OracleAS Web Cache.

WXE-09573 Unexpected File I/O Error ( %s ) when unlinking file %s.

Severity: notification

Cause: Unexpected I/O file error.

Action: Review the specified error and correct the problem on the system.

WXE-09574 Permission denied when unlinking file %s.

Severity: notification

Cause: Permission denied on file.

Action: Set correct permission on the specified file.

WXE-09600 SIGTERM caught - program will shut down once all connections are complete.

Severity: notification

Cause: Normal notification behavior. Shutdown event written to the log file.

Action: No action required.

WXE-09601 SIGUSR1 caught - program will reread configuration files after all connections are complete.

Severity: notification

Cause: Normal notification behavior. Configuration file reread event written to the log file.

Action: No action required.

WXE-09602 All configuration files have been reread.

Severity: notification

Cause: Normal notification behavior. All configuration files have been reread and this configuration reload event written to the log file.

Action: No action required.

WXE-09603 There was an error rereading the configuration files. The program is exiting.

Severity: alert

Cause: Invalid OracleAS Web Cache configuration files.

Action: Correct the OracleAS Web Cache configuration files and restart OracleAS Web Cache.

WXE-09604 Could not increase the number of file/socket descriptors to %s.

Severity: alert

Cause: Ran out of file descriptors on the system.

Action: Decrease the Maximum Incoming Connections value in the OracleAS Web Cache Manager, or increase the system file descriptors. Run OracleAS Web Cache as the root user.

WXE-09605 Cannot create OPMN shutdown thread. Continuing with startup.

Severity: notification

Cause: OracleAS Web Cache could not create OPMN shutdown thread.

Action: Use OPMN to abort the OracleAS Web Cache process during OracleAS Web Cache shutdown.

WXE-09606 Cannot create OPMN shutdown event. Continuing with startup.

Severity: notification

Cause: OracleAS Web Cache could not create OPMN shutdown event.

Action: Use OPMN to abort the OracleAS Web Cache process during OracleAS Web Cache shutdown.

WXE-09607 The admin server started successfully.

Severity: notification

Cause: The OracleAS Web Cache admin server process started successfully.

Action: No action required.

WXE-09608 The cache server process started successfully.

Severity: notification

Cause: The OracleAS Web Cache server process has started successfully.

Action: No action required.

WXE-09609 The server process could not initialize.

Severity: alert

Cause: The OracleAS Web Cache configuration is invalid.

Action: Review the error log file or use the Event Viewer to help determine the cause of the problem.

WXE-09610 The server is exiting.

Severity: notification

Cause: The cache server or admin server process is terminating.

Action: Review the error log file or use the Event Viewer to help determine the cause of the problem.

WXE-09611 The server could not start the service thread.

Severity: alert

Cause: The server process could not start the Service thread.

Action: Determine why OracleAS Web Cache cannot start a thread on your system.

WXE-09612 OracleAS Web Cache version number: %s

Severity: notification

Cause: Normal notification behavior. The OracleAS Web Cache version number was written to the log file.

Action: No action required.

WXE-09614 The following OracleAS Web Cache internal files are preseeded into the cache: %s

Severity: notification

Cause: The specified OracleAS Web Cache internal files are loaded into the cache.

Action: No required action.

WXE-09700 Unable to initialize NLS. Error %d

Severity: alert

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support Services.

WXE-09701 Unable to initialize NLS global structure.

Severity: alert

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support Services.

WXE-09702 NLS boot file not found or missing; using default.

Severity: warning

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support Services.

WXE-09703 Stop Issued. The program will shut down after all accepted requests are served, or a timeout occurs.

Severity: notification

Cause: Stop was issued.

Action: OracleAS Web Cache will be stopped.

WXE-09704 Abort Issued. The program will shut down immediately.

Severity: notification

Cause: Abort was issued.

Action: OracleAS Web Cache will be stopped immediately.

WXE-09705 Error accessing the Oracle Notification Service library, %s: %s

Severity: alert

Cause: An error occurred when attempting to open or access functions in the Oracle Notification Service (ONS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found" or "function not available".

Action: If the problem persists, contact Oracle Support Services.

WXE-09706 Ignoring unrecognized option: %s

Severity: alert

Cause: An alert was logged.

Action: Refer to the logged alert details and take the appropriate action.

WXE-09707 Failed to start the server.

Severity: alert

Cause: Failed to start the OracleAS Web Cache server. This error usually occurs as a result of insufficient system resources or invalid configuration.

Action: If the problem persists, contact Oracle Support Services.

WXE-09708 Failed to initialize DNS

Severity: alert

Cause: Failed to initialize DNS.

Action: If the problem persists, contact Oracle Support Services.

WXE-09709 Failed to initialize the HTTP component

Severity: alert

Cause: Failed to initialize HTTP.

Action: If the problem persists, contact Oracle Support Services.

WXE-09710 Cache server failed to initialize.

Severity: alert

Cause: Insufficient system resources or invalid OracleAS Web Cache configuration.

Action: Review the error log file or use the Event Viewer to help determine the cause of the problem.

WXE-09711 Problem loading message file for event log. Exiting.

Severity: alert

Cause: Message file for event log was not correctly loaded.

Action: Check the existence of the file $ORACLE_HOME/webcache/mesg/wxeus.msb and permissions for it.

WXE-09712 Unable to open the Oracle Notification Service library, %s:%s. Searching the library path.

Severity: warning

Cause: An error occurred when attempting to open the Oracle Notification Service (ONS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found". OracleAS Web Cache will search the library path. If the library is still not found, then OracleAS Web Cache returns error message WXE-09705.

Action: If the problem persists, contact Oracle Support Services.

WXE-10054 Unable to resume service, UIPI return value is %s.

Severity: alert

Cause: Service could not be resumed.

Action: Review the error to determine the problem on your system.

WXE-10417 MIME Type Extension ( %s ) exceeds current size limit.

Severity: warning

Cause: Unexpected MIME type configured.

Action: No action required.

WXE-10418 Encoding Extension ( %s ) exceeds current size limit.

Severity: warning

Cause: Unexpected encoding type configured.

Action: No action required.

WXE-10419 Language Extension ( %s ) exceeds current size limit.

Severity: warning

Cause: Unexpected language type configured.

Action: No action required.

WXE-10536 You must specify a full path for %s. See %s %s.

Severity: alert

Cause: Failed to specify full path name.

Action: Specify a full path name for the file.

WXE-10555 Bad integer value ( %s ). See %s %s.

Severity: alert

Cause: Invalid drive letter.

Action: Contact Oracle Support Services.

WXE-10599 Unexpected error

Severity: alert

Cause: Unexpected internal error.

Action: Contact Oracle Support Services.

WXE-11058 Stale document updated for %s%s

Severity: trace

Cause: The complete response was successfully received and the cache entry is updated with the new response.

Action: No action required.

WXE-11059 Garbage document updated for %s%s

Severity: trace

Cause: The complete response was successfully received and the cache entry is updated with the new response.

Action: No action required.

WXE-11060 Document update aborted for %s%s.

Severity: trace

Cause: The response will not be used to update the stale or garbage document in the cache because it was determined that it is not cacheable.

Action: No action required.

WXE-11061 Document compression error: %s

Severity: error

Cause: A gzip library call has failed.

Action: If the problem persists, contact Oracle Support Services.

WXE-11062 <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tag parsing error

Severity: warning

Cause: The syntax for the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags was incorrect.

Action: Correct the syntax of the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags in the source.

WXE-11063 Document compressed: original size: %d bytes; compressed size: %d bytes.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11064 ESI document %s%s parsing error

Severity: warning

Cause: Document contained invalid ESI syntax.

Action: Correct the ESI syntax in the source.

WXE-11076 Cluster member %s - %s sent invalid configuration error

Severity: warning

Cause: The cache cluster member sent a response to OracleAS Web Cache that indicates it has a configuration file different than the local configuration file for the cache cluster. A cluster runtime operates with the same webcache.xml configuration file for all members.

Action: Compare the two configuration files, and then propagate the proper version to all cluster members.

WXE-11077 Cluster member sent invalid configuration error

Severity: warning

Cause: The cache cluster member sent a response to OracleAS Web Cache that indicates it has a configuration file different than the local configuration file for the cache cluster. A cluster runtime operates with the same webcache.xml configuration file for all members.

Action: Compare the two configuration files, and then propagate the proper version to all cluster members.

WXE-11078 Malformed environment document %s%s

Severity: warning

Cause: The syntax of the XML file specified by the ESI environment is incorrect.

Action: Check the XML document for possible syntax errors.

WXE-11083 Proxy server configuration error: %s

Severity: error

Cause: The proxy server was not correctly configured.

Action: Check the proxy server configuration in the Proxy Servers page of OracleAS Web Cache Manager and the general configuration of the proxy server itself.

WXE-11085 Authentication for the remote or subscriber cache is being challenged by a central or provider cache. Retry.

Severity: trace

Cause: Access to the central or provider cache requires authorization.

Action: Try accessing the cache again.

WXE-11088 Following URL is now in cache:

Severity: trace

Cause: The complete response was successfully received and populated into the cache.

Action: No action required.

WXE-11089 Error while sending the entity body to the origin server

Severity: error

Cause: OracleAS Web Cache encountered a bad network connection or the origin server was down.

Action: No action required

WXE-11091 Error while processing ESI for %s%s

Severity: warning

Cause: An error was encountered while ESI processing was done for the response. The page will not be cached.

Action: No action required.

WXE-11092 Document validated for %s%s

Severity: trace

Cause: The cached document was validated by the origin server and its expiration timestamps were updated accordingly.

Action: No action required.

WXE-11093 Content-Length value %d sent by origin server does not match number of bytes received, that is %d bytes for %s%s.

Severity: warning

Cause: This error can occur if the origin server sent an incorrect Content-Length value or if the connection was unexpectedly terminated.

Action: Check that the origin server is sending the correct Content-Length for the URL mentioned.

WXE-11110 The maximum cache size is set too low. OracleAS Web Cache failed to initialize.

Severity: alert

Cause: The maximum cache size is set too low. Some of the data structures could not be initialized because of insufficient memory. This error could also be caused by changes to the file internal.xml.

Action: Increase the maximum cache size. If this fails, revert to the original values in internal.xml. Contact Oracle Support Services for information about the internal.xml file.

WXE-11111 Based on Maximum Cache Size value %s in the Resource Limits page of OracleAS Web Cache Manager, a cache table is created.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11114 Non-cacheable entry removed from the cache miss table during voluntarily garbage collection is

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11115 Request to perform voluntary garbage collection of non-cacheable table is submitted.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11118 Duplicate search key %s found in Surrogate-Key response header is discarded.

Severity: error

Cause: A duplicate search key was discovered in the Surrogate-Key response header.

Action: Remove the duplicate search key token from Surrogate-Key response header.

WXE-11119 The number of search keys changed.

Severity: warning

Cause: The number of search keys has changed for the same cached document.

Action: No action required.

WXE-11128 A duplicate cache insertion is found. Cache insertion fails.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11201 OracleAS Web Cache is unable to resolve the IP address of %s. Check your DNS setup.

Severity: alert

Cause: OracleAS Web Cache was unable to resolve the IP address of the origin server.

Action: Check whether the origin server is a valid host. You can alter origin server configuration in the Origin Servers page of OracleAS Web Cache Manager.

WXE-11202 Origin server %s does not use IPv4.

Severity: alert

Cause: OracleAS Web Cache only supports IP version 4. The IP address of the origin server could not be resolved because it used another version of IP.

Action: Check that the origin server is a valid host and check the DNS setup. You can alter origin server configuration in the Origin Servers page of OracleAS Web Cache Manager.

WXE-11203 OracleAS Web Cache fails to connect to the origin server (id=%d).

Severity: warning

Cause: An origin server is not available.

Action: Check the status of the origin server and the network connection.

WXE-11205 OracleAS Web Cache marked the origin server %s:%u (id=%d) as down and removed all session information bound to it.

Severity: trace

Cause: The origin server was disabled or reached its failover threshold. OracleAS Web Cache automatically distributes the request load over the remaining origin servers and polls the failed origin server for its current status.

Action: No action required.

WXE-11206 OracleAS Web Cache is unable to start pinging the origin server. rc code=%d

Severity: alert

Cause: There was a potential memory allocation error.

Action: Check the configured memory usage in the Resource Limits page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11207 Origin server %s:%u (id=%d) is down; OracleAS Web Cache starts polling for status.

Severity: warning

Cause: The origin server reached its failover threshold. OracleAS Web Cache automatically distributes the request load over the remaining origin servers and polls the failed origin server for its current status.

Action: No action required.

WXE-11208 Cache cluster member %s (id=%d) is down; cache cluster members start polling for status.

Severity: warning

Cause: The cache cluster member reached its failover threshold. OracleAS Web Cache reassigns ownership of cache content, and polls the failed cache cluster member for its status.

Action: No action required.

WXE-11209 Origin server %s:%u (id=%d) is back up; OracleAS Web Cache stops polling and restores origin server.

Severity: warning

Cause: The ping URL to the origin server succeeded.

Action: No action required.

WXE-11210 Cache cluster member %s (id=%d) is up; cache cluster members stop polling and restore it.

Severity: warning

Cause: The ping URL to the cache cluster member succeeded.

Action: No action required.

WXE-11211 All origin servers for site %s are down. Last origin server was (id=%d).

Severity: warning

Cause: All origin servers configured for the site are down.

Action: No action required.

WXE-11220 Session binding routing to origin server %s:%u (id=%d) for site %s

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11221 The origin server request is queued for site %s and site-to-server mapping %s.

Severity: trace

Cause: The origin server was busy.

Action: No action required.

WXE-11222 The origin server request is dropped due to a full queue for site %s and site pattern %s.

Severity: trace

Cause: The origin server request queue was full.

Action: No action required.

WXE-11223 The origin server request is routed to peer cache cluster member %s (id=%d) for site %s.

Severity: trace

Cause: The request did not support session binding, and the requested document was owned by the peer cache cluster member.

Action: No action required.

WXE-11224 Site %s matches site-to-server mapping %s.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11225 OracleAS Web Cache cannot find any running origin servers to route the request for site %s.

Severity: warning

Cause: All origin servers are down.

Action: No action required.

WXE-11226 The session binding request is to a busy origin server %s:%u (id=%d) for site %s.

Severity: trace

Cause: The session binding request was to a server was that was busy.

Action: No action required.

WXE-11227 Request is routed to origin server %s:%u using load balancing.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11228 No defined origin server can serve this request for site %s. The request is dropped.

Severity: trace

Cause: This request was not an ESI template and could not be served by dynamic origin servers for ESI provider sites.

Action: No action required.

WXE-11229 This ESI fragment request is forwarded to a dynamic origin server for ESI provider site %s.

Severity: trace

Cause: The request was for an ESI fragment without a matching site-to-server mapping.

Action: No action required.

WXE-11240 Origin server %s:%u (id=%d) has %d connections timed out or closed for other reasons.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11250 ESI include fragment protocol does not match origin server protocol: Origin Server Protocol=%s URL=%s%s%s

Severity: warning

Cause: The protocol used in the src attribute does not match the protocol specified in the Site-to-Server Mapping page of OracleAS Web Cache Manager. OracleAS Web Cache used the protocol configured for the origin server in the Site-to-Server Mapping page.

Action: Correct the protocol in the template for the fragment.

WXE-11260 Session binding cookie name %s with cookie value %s exceeds limit %d.

Severity: warning

Cause: The cookie name and value exceeded the allowed length limit in OracleAS Web Cache.

Action: Contact Oracle Support Services.

WXE-11261 Session binding query string parameter name %s with value %s exceeds limit %d.

Severity: warning

Cause: The query string parameter name and value exceeded the allowed length limit in OracleAS Web Cache.

Action: Contact Oracle Support Services.

WXE-11270 Cache cluster member %s (id=%d) sent a peer member a configuration error in the response.

Severity: warning

Cause: The response from a cache cluster member specified that its configuration did not match the configuration of a peer cache cluster member. This mismatch typically occurs because the configuration has not been propagated. You propagate configuration in the Cache Operations page of OracleAS Web Cache Manager.

Action: Contact Oracle Support Services.

WXE-11290 OracleAS Web Cache DNS cache miss. Scheduling DNS task for host name %s

Severity: trace

Cause: The entry for the host name was stale or missing in OracleAS Web Cache's DNS cache. OracleAS Web Cache scheduled a DNS task to get the host name.

Action: No action required.

WXE-11291 DNS lookup task scheduling fails for host %s.

Severity: alert

Cause: Asynchronous task scheduling failed.

Action: Check the log of corresponding asynchronous task scheduling.

WXE-11292 DNS lookup succeeds for host %s.

Severity: trace

Cause: The DNS cache miss and lookup succeeded.

Action: No action required.

WXE-11293 OracleAS Web Cache fails to connect to dynamic origin server for ESI provider site and again performs a DNS lookup for host %s.

Severity: trace

Cause: There was a possible stale DNS cache entry.

Action: No action required.

WXE-11294 OracleAS Web Cache fails to connect to a dynamic origin server for ESI provider site with fresh DNS lookup result for host %s.

Severity: alert

Cause: There was a potential system DNS error or invalid host.

Action: 1. Check whether the host is valid. 2. In a deployment environment, try to connect to this host and port. If the connection succeeds, then check the system/network DNS setup. 3. If problem persists, contact Oracle Support Services.

WXE-11295 OracleAS Web Cache failed in DNS lookup for host %s.

Severity: warning

Cause: There was a potential system DNS error or invalid host.

Action: 1. Check whether the host is valid. 2. In a deployment environment, try to connect to this host and port. If the connection succeeds, then check the system/network DNS setup. 3. If problem persists, contact Oracle Support Services.

WXE-11300 The attempt to create an entry in the cache failed due to low memory.

Severity: alert

Cause: Memory low during insertion.

Action: No action required.

WXE-11303 Request method is not GET nor POST nor PUT; tunneling.

Severity: trace

Cause: The HTTP method in the request is not one of GET, POST or PUT. OracleAS Web Cache will tunnel this request between the client and the origin server.

Action: No action required.

WXE-11304 Cache miss request.

Severity: trace

Cause: The cache did not have a document matching the request.

Action: No action required.

WXE-11306 Request is for a non-cacheable object, forwarding request to the backend.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11308 Request may not be cacheable according to caching rule.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-11312 invalid Oracle-ECID request header

Severity: error

Cause: OracleAS Web Cache was unable to parse the Oracle-ECID request header.

Action: Correct the syntax of the Oracle-ECID request header.

WXE-11313 The cache server reached the maximum number of allowed incoming connections. Listening is temporarily suspended.

Severity: alert

Cause: The cache server reached the maximum number of incoming connections specified in the Resource Limits page.

Action: Try again later. If this message persists, increase the Maximum Incoming Connections in the Resource Limits page of OracleAS Web Cache Manager.

WXE-11314 Listening has resumed.

Severity: alert

Cause: The number of incoming connection count is under the threshold, enabling the cache server to accept new requests from browsers.

Action: No action required.

WXE-11321 Connection from browser cannot be established.

Severity: error

Cause: The handshake with the browser failed.

Action: No action required.

WXE-11330 The host request header %s is an alias for configured site %s.

Severity: trace

Cause: The alias for the site matched the Host request header.

Action: No action required.

WXE-11331 Host request header matches configured site %s.

Severity: trace

Cause: The Host request header matched the site name.

Action: No action required.

WXE-11332 Failed to rewrite URI from '%s' to '%s' according to rewrite rule '%s'. The original URI will be used.

Severity: warning

Cause: URI rewrite failed. OracleAS Web Cache will use the original URI in subsequent operations without rewriting.

Action: Modify URL rewrite rules.

WXE-11333 URI is rewritten from %s to %s according to rewrite rule %s.

Severity: trace

Cause: URI rewrite was successful.

Action: No action required.

WXE-11334 User-Agent request header %s does not match any rule. OracleAS Web Cache remapped User-Agent to the default value %s.

Severity: trace

Cause: User-Agent request header did not match any rule.

Action: Manually modify user-agent rules in the webcache.xml file.

WXE-11335 User-Agent request header remapped from %s to %s according to mapping rule %s.

Severity: trace

Cause: User-Agent request header matched a rule.

Action: No action required.

WXE-11337 Administration service unavailable. Try again later.

Severity: warning

Cause: There were too many administration requests.

Action: Ensure that only one user is the administrator user.

WXE-11338 URL is in the cache

Severity: trace

Cause: There was a matching entry in the cache for this request.

Action: No action required.

WXE-11339 OracleAS Web Cache determined the request might be cacheable based on existing cache policy.

Severity: trace

Cause: There was no matching cache entry for this request. However, based on existing cache policy, OracleAS Web Cache determined that it is likely to be cacheable.

Action: No action required.

WXE-11340 A new entry in the cache is created.

Severity: trace

Cause: OracleAS Web Cache created an entry in the cache for this request.

Action: No action required.

WXE-11342 OracleAS Web Cache determined the request might not be cacheable based on existing cache policy.

Severity: trace

Cause: There was no matching cache entry for this request. However, based on existing cache policy, OracleAS Web Cache determined that it is likely to be not cacheable.

Action: No action required.

WXE-11343 The requested site does not have a matching origin server mapping. A bad request error will be returned.

Severity: error

Cause: There was no matching site-to-server mapping for this non-ESI-fragment request.

Action: No action required.

WXE-11344 Returning a freshly cached document.

Severity: trace

Cause: The cached document will be returned because it is still fresh.

Action: No action required.

WXE-11345 The cached document is stale and this request will be served stale.

Severity: trace

Cause: The cached document is stale and OracleAS Web Cache decided to serve the stale copy to the request.

Action: No action required.

WXE-11346 The cached document is stale and an origin server will be contacted for a fresh copy.

Severity: trace

Cause: Because the cached document is stale, OracleAS Web Cache fetched a new version of the document to update the cache and satisfy this request with the new response.

Action: No action required.

WXE-11347 The cached document is garbage.

Severity: trace

Cause: The cached document is in garbage state, meaning that it could not be used to serve to the client.

Action: No action required.

WXE-11348 There is already another pending request for the same document being forwarded to the origin server for a fresh copy. This request will wait for the fresh copy.

Severity: trace

Cause: The cached document is in garbage state, and there is another request for the same document being forwarded to the origin server for a fresh copy to update the cache. Therefore, this request will wait until the fresh copy arrives.

Action: No action required.

WXE-11349 The request will be forwarded to the origin server to obtain a fresh copy of the document.

Severity: trace

Cause: The cached document was in garbage state, and there was no other request pending to update the cache. OracleAS Web Cache will forward this request to the origin server for a fresh copy of the document to update the cache and satisfy this request with the new response.

Action: No action required.

WXE-11350 The request contains no site information in the URL or Host header. The configuration of the default site %s will be used.

Severity: trace

Cause: The request did not contain a Host header, nor did it have an absolute URL that contained a site name. OracleAS Web Cache will use the default site in the configuration for this request.

Action: No action required.

WXE-11351 The complete site name is: %s

Severity: trace

Cause: The complete site name was resolved based on the configuration.

Action: No action required.

WXE-11352 There is no matching defined site or aliases in the configuration for this request.

Severity: trace

Cause: The configuration did not contain a matching site definition for the request. The site name will be taken from the request as is.

Action: No action required.

WXE-11354 Out of memory while processing the request. A service unavailable response is returned to the client. Client IP: %s

Severity: alert

Cause: OracleAS Web Cache failed to obtain enough memory while processing the request.

Action: Adjust the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11355 Single request header length exceeds configured maximum. A forbidden error response is returned to the client. Client IP: %s

Severity: error

Cause: One of the headers in the request exceeded the configured maximum.

Action: Adjust the maximum individual header size limit in the Security page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11356 Total request header length exceeds configured maximum. A forbidden error response is returned to the client. Client IP: %s

Severity: error

Cause: The total length of the headers in the request exceeded the configured maximum.

Action: Adjust the maximum combined header size limit in the Security page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11357 Failed to resolve the requested site name. A bad host error response is returned to the client.

Severity: error

Cause: The request did not contain enough information about the site name.

Action: No action required.

WXE-11358 Failed client certificate check. A forbidden error response is returned.

Severity: error

Cause: The request was for a URL that requires a client certificate, and the certificate check failed for this request.

Action: No action required.

WXE-11359 Host header missing in HTTP/1.1 request. A bad host error response is returned.

Severity: error

Cause: The request was an HTTP/1.1 request, but is missing the required Host header.

Action: No action required.

WXE-11360 Error processing the Transfer-Encoding header in the request. A bad request error response is returned.

Severity: error

Cause: An error was encountered while processing the Transfer-Encoding header in the request.

Action: No action required.

WXE-11361 Transfer-Encoding specified in the request is not supported. An HTTP not implemented error response is returned.

Severity: error

Cause: OracleAS Web Cache only supports chunked encoding. Other types transfer encoding are not supported.

Action: No action required.

WXE-11362 Malformed request. A bad request error response is returned. Client IP: %s

Severity: error

Cause: The request was malformed.

Action: No action required.

WXE-11363 Out of memory while processing the request. The request is dropped.

Severity: error

Cause: OracleAS Web Cache failed to obtain enough memory while processing the request.

Action: Adjust the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11364 Network error response is returned.

Severity: error

Cause: A network error was encountered while processing the request.

Action: Check other error messages related to this request.

WXE-11365 Server busy response is returned.

Severity: error

Cause: The origin servers for the requested site were at full capacity, and the waiting queue was full.

Action: Increase the capacity of the origin servers.

WXE-11367 No matching origin server can be found for the requested site. A bad host error response is returned

Severity: error

Cause: The requested site did not have any matching origin servers in the configuration.

Action: Modify the Site-to-Server Mapping page of OracleAS Web Cache Manager.

WXE-11368 ESI exception error response is returned.

Severity: error

Cause: An ESI exception was encountered while processing the request.

Action: Check other error messages related to this request.

WXE-11369 The request method is not supported. An HTTP not implemented error response is returned.

Severity: error

Cause: The request specified an unsupported method.

Action: No action required.

WXE-11370 A chunk-encoded request entity body contains a chunk that exceeds %u bytes. A bad request error response is returned. Client IP: %s

Severity: error

Cause: This chunk-encoded request contained a chunk that exceeded the DOCHEADERBUFFERSIZE setting in internal.xml

Action: Consider increasing DOCHEADERBUFFERSIZE.

WXE-11371 Malformed request. The chunk-encoded request entity body contains a line feed without a preceding carriage return. A bad request error response is returned. Client IP: %s

Severity: error

Cause: The request is malformed.

Action: none

WXE-11372 Aborting origin server request

Severity: warning

Cause: A request sent to OracleAS Web Cache was aborted. Because OracleAS Web Cache was in the process of forwarding the request to an origin server, the request to the origin server was also aborted.

Action: No action required.

WXE-11373 This request %s is not being enabled with End-User Performance Monitoring

Severity: warning

Cause: A single response from the origin server to OracleAS Web Cache was not enabled for End-User Performance Monitoring because of a software limitation.

Action: No action required.

WXE-11400 non-200 OK HTTP status code response code of %d

Severity: trace

Cause: The response received from the origin server contained a HTTP status code other than 200 OK.

Action: If this is not the intended response, then check the application code.

WXE-11403 begin cacheability decision for following url:

Severity: trace

Cause: This marks the start of the cacheability decision for the specified URL. All messages logged between this message and the "final cacheability decision made" message are about the same request/response pair.

Action: No action required.

WXE-11404 Time %s in the Last-Modified header is after the current time. The cache is using the current time instead.

Severity: warning

Cause: The Last-Modified response header received from the origin server contained a time that is in the future. The cache used the current time as the last-modified time instead.

Action: Check the application code that generates the Last-Modified response header.

WXE-11406 URL matches no-cache rule "%s".

Severity: trace

Cause: The request URL matched a non-cacheable caching rule.

Action: No action required.

WXE-11407 URL matches caching rule "%s".

Severity: trace

Cause: The request URL matched a cacheable caching rule.

Action: No action required.

WXE-11408 URL does not match any caching rule.

Severity: trace

Cause: The request URL did not match any configured caching rule.

Action: If this is not the intended behavior, then check the configured caching rules.

WXE-11409 HTTP POST request body length %d exceeds maximum cacheable limit. %d.

Severity: trace

Cause: The POST body length in the request exceeded the maximum cacheable limit for a POST body. Therefore, the corresponding response was not cached.

Action: If this response needs to be cached, contact Oracle Support Services.

WXE-11410 Response contains cookie "%s=%s", which is not present in the request.

Severity: trace

Cause: The response received from the origin server contained a newly created cookie that was not present in the request. As a result, OracleAS Web Cache considered the response to be non-cacheable.

Action: No action required.

WXE-11411 Response contains cookie "%s=%s", which does not match the same cookie value "%s" in the request.

Severity: trace

Cause: The response received from the origin server contained a new cookie that is different from the cookie value in the request. As a result, OracleAS Web Cache considered the response to be non-cacheable.

Action: No action required.

WXE-11412 The Surrogate-Control header conflicts with the previously saved caching rule. This response is not cacheable while a new policy is created.

Severity: trace

Cause: The Surrogate-Control header in the response contained control directives that are in conflict with the previously saved caching rule. This response will not be cached until OracleAS Web Cache creates a new cache policy to replace the old one.

Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.

WXE-11413 The HTTP request method is not GET, or the URL contains query string parameters. The request is not cacheable.

Severity: trace

Cause: The request used an HTTP method that was neither GET nor POST. As a result, OracleAS Web Cache considered it to be non-cacheable.

Action: No action required.

WXE-11414 Initial cache key is composed:

Severity: trace

Cause: The initial cache key was composed of the complete site name, the URL, the HTTP request method, and the POST body, if any.

Action: No action required.

WXE-11415 Final cache key is composed:

Severity: trace

Cause: The final cache key was composed of the initial cache key plus any cookies and headers as specified by caching rule.

Action: No action required.

WXE-11416 The response is considered not cacheable due to the lack of caching directives.

Severity: trace

Cause: The response did not contain any headers with caching directives and had no matching caching rule. As a result, OracleAS Web Cache considered it to be non-cacheable.

Action: No action required.

WXE-11417 URL is not cacheable based on its HTTP headers.

Severity: trace

Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, OracleAS Web Cache considered it to be non-cacheable.

Action: No action required.

WXE-11418 The response contains a Surrogate-Control header with either a no-store control directive or a zero-value max-age control directive, indicating that the response is non-cacheable.

Severity: trace

Cause: The response contained a Surrogate-Control header with either a no-store control directive or a zero-value max-age control directive. As a result, OracleAS Web Cache considered it to be non-cacheable.

Action: No action required.

WXE-11419 The Surrogate-Control header contains a nonzero max-age=%d+%d control directive, indicating that the response is cacheable.

Severity: trace

Cause: The response contained a Surrogate-Control header with a nonzero max-age directive. As a result, OracleAS Web Cache considered it to be cacheable.

Action: No action required.

WXE-11420 The response contains Surrogate-Control header with a zero-value max-age control directive and Etag header, indicating that the response is cacheable with validation.

Severity: trace

Cause: The response contained Surrogate-Control header with a zero-value max-age control directive and Etag header. As a result, OracleAS Web Cache considered it to be cacheable with validation.

Action: No action required.

WXE-11422 The Surrogate-Control header contains the vary control directive, overriding configuration.

Severity: trace

Cause: The response Surrogate-Control header contained the vary control directive. It is used in place of the existing caching rule.

Action: No action required.

WXE-11423 OracleAS Web Cache ran out of memory while creating caching rule according to the vary control directive of the Surrogate-Control header.

Severity: alert

Cause: There was not sufficient memory for OracleAS Web Cache to process the vary control directive.

Action: Adjust the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11424 The request contains session %s, which makes it non-cacheable based on the existing caching rule.

Severity: trace

Cause: The current caching rule for this URL specified that if a specific session exists in the request, then the request is treated as non-cacheable.

Action: No action required.

WXE-11425 The request does not contain session %s, which makes it non-cacheable based on the existing caching rule.

Severity: trace

Cause: The current caching rule for this URL specified that if a specific session did not exist in the request, the request is treated as non-cacheable.

Action: No action required.

WXE-11426 The request does not contain cookie %s, which makes it non-cacheable based on the existing caching rule.

Severity: trace

Cause: The current caching rule for this URL specified that if a specific cookie does not exist in the request, the request is treated as non-cacheable.

Action: No action required.

WXE-11427 The request does not contain HTTP request header %s, which makes it non-cacheable based on the existing caching rule.

Severity: trace

Cause: The current caching rule for this URL specified that if a specific header does not exist in the request, the request was treated as non-cacheable.

Action: No action required.

WXE-11431 In absence of any overriding headers in the response, the response is not cacheable based on the existing caching rule.

Severity: trace

Cause: The response was not cacheable because the matching caching rule indicates so, and there are no overriding response headers in the response to override the caching rule.

Action: No action required.

WXE-11432 The regular HTTP response headers indicate that the response is cacheable.

Severity: trace

Cause: The response contained regular HTTP headers that indicate it is cacheable.

Action: No action required.

WXE-11433 The response size %d is too large to be cacheable.

Severity: trace

Cause: The response body size was greater than the maximum cacheable document size.

Action: If this is not the desired behavior, increase the Maximum Cached Object Size value in the Resource Limits page of OracleAS Web Cache Manager.

WXE-11434 The ESI include or inline tag for this fragment contains reference TTL=%d+%d, making the fragment cacheable.

Severity: trace

Cause: The ESI include or inline tag for the fragment contained a nonzero reference TTL. As a result, OracleAS Web Cache considered the fragment cacheable.

Action: No action required.

WXE-11442 The response could not be parsed.

Severity: trace

Cause: The Surrogate-Control response header contained a content type but a Content header is not text or HTML.

Action: If the content needs to be parsed, send the text or HTML in the Content header.

WXE-11443 The request does not contain header %s, which makes it non-cacheable based on the vary control directive in the Surrogate-Control response header.

Severity: trace

Cause: The request was missing a required header to be cacheable based on the vary control directive in the Surrogate-Control response header.

Action: No action required.

WXE-11444 The request does not contain cookie %s, which makes it non-cacheable based on the vary control directive in the Surrogate-Control response header.

Severity: trace

Cause: The request was missing a required cookie to be cacheable based on the vary control directive in the Surrogate-Control response header.

Action: No action required.

WXE-11445 Following URL will not be cached:

Severity: trace

Cause: The final cacheability decision for this response is not cacheable.

Action: No action required.

WXE-11446 URL which will be cached is:

Severity: trace

Cause: The final cacheability decision for this response is cacheable.

Action: No action required.

WXE-11500 StatisticsTimerInterval configuration parameter should be between 10,000 and 1,000,000 microseconds, and should be a factor of 1,000,000

Severity: alert

Cause: Illegal configuration parameter for statistics timer interval.

Action: This error usually occurs as a result of wrong configuration. Contact Oracle Support Services.

WXE-11501 While getting detailed memory statistics, pointer swapped while filling HTML

Severity: notification

Cause: While retrieving detailed memory statistics, the timer pointer swapped to a new index as it was filling the HTML template.

Action: No action required.

WXE-11502 Unable to create or open file %s for write. Cache contents not written.

Severity: error

Cause: The cache server was unable to open the file specified. Either the file already exists and the OracleAS Web Cache user does not have write permission on the file or the OracleAS Web Cache user does not have write permission to the directory.

Action: Check permissions on the file and the directory and correct them to allow OracleAS Web Cache to create the file or write to it.

WXE-11503 Abnormal statistics value of %s was detected. Value 0 was recorded.

Severity: alert

Cause: Internal error. The statistics value that was returned was an abnormal (negative) value.

Action: If the problem persists, contact Oracle Support Services.

WXE-11700 Client IP checking fails. Access denied.

Severity: error

Cause: OracleAS Web Cache allows invalidation to be sent from configured IP groups. The current invalidation message was not sent from an IP address that belongs to the configured groups.

Action: Configure trusted hosts in the Security page of OracleAS Web Cache Manager.

WXE-11701 Authentication failed. Invalid username or password.

Severity: error

Cause: The invalidation message contained an incorrect username or password.

Action: Resend the invalidation message with the correct invalidator user name and password. You can change the password in the Security page of OracleAS Web Cache Manager.

WXE-11702 The invalidation request contains an empty request body.

Severity: error

Cause: The invalidation request contained an empty request body.

Action: Resend the invalidation request with a request body.

WXE-11703 Invalidation request specifies a wrong URL.

Severity: error

Cause: The invalidation message carried a wrong request URL.

Action: No action required.

WXE-11704 Invalidation message contains XML parsing errors.

Severity: error

Cause: The invalidation message contained invalid XML.

Action: Correct the XML errors in the invalidation message.

WXE-11705 Invalid validity level '%s' is requested.

Severity: error

Cause: The invalidation message specified an invalid validity level. The correct range of level is between 0 and 9.

Action: Correct the message to use a validity level between 0 to 9.

WXE-11706 %d object(s) matching prefix '%s' are invalidated.

Severity: notification

Cause: Invalidation of objects was successful.

Action: No action required.

WXE-11707 Object with URL '%s' is successfully invalidated.

Severity: notification

Cause: Invalidation was successful.

Action: No action required.

WXE-11708 Object with URL '%s' is not cacheable. Invalidation is not done.

Severity: notification

Cause: The URL was not a cacheable object. Invalidation is not performed for non-cacheable objects.

Action: No action required.

WXE-11710 Object with URL '%s' not in the cache. Invalidation is not performed.

Severity: notification

Cause: The object was not in the cache. Invalidation is not performed for non-cacheable objects.

Action: No action required.

WXE-11711 OracleAS Web Cache cannot compose key pattern for requested URL '%s'.

Severity: error

Cause: OracleAS Web Cache could not compose a key pattern for requested URL expression.

Action: Correct the URL expression in the invalidation message.

WXE-11712 Invalidation message contains unrecognized cookies.

Severity: error

Cause: The invalidation message contained nonexistent cookies.

Action: Correct the cookie name specified in the invalidation message.

WXE-11713 Invalid regular expression found in invalidation message. %s

Severity: error

Cause: The invalidation message contained an invalid regular expression that could not be compiled.

Action: Correct the regular expression in the invalidation message.

WXE-11715 Regular expression matching error. Error number: %d

Severity: error

Cause: The regular expression in the invalidation message was invalid. OracleAS Web Cache could not perform regular expression matching successfully.

Action: Check regexec man page with error number for syntax error description.

WXE-11716 Invalidation XML message cannot be parsed.

Severity: error

Cause: Invalidation XML message could not be parsed.

Action: No action required.

WXE-11717 Invalidation XML error found in invalidation message.

Severity: error

Cause: OracleAS Web Cache received an invalidation message in an old version. It is unable to obtain all information about the URL node.

Action: Correct the invalidation message or use an invalidation version of either "WCS-1.1" or "WCS-1.0".

WXE-11721 Cannot read value for XML element/attribute: '%s'.

Severity: error

Cause: OracleAS Web Cache was unable to obtain all information about the specified XML element or attribute.

Action: Correct the XML in the invalidation message.

WXE-11722 Invalidation message specifies unknown version: '%s'.

Severity: error

Cause: The invalidation message specified an unknown version.

Action: Correct the invalidation message to use version "WCS-1.1" or "WCS-1.0".

WXE-11723 Value of XML string '%s' too long. Actual length: %d, max length allowed: %d.

Severity: error

Cause: The XML string in the invalidation message exceeded the allowed length limit.

Action: Correct the XML in the invalidation message.

WXE-11724 URL path prefix does not end with '/': '%s'.

Severity: error

Cause: The URL path prefix did not end with '/' in the invalidation message.

Action: Correct the syntax of the URL path prefix in the invalidation message.

WXE-11725 Cannot create XML element/attribute: '%s'.

Severity: error

Cause: OracleAS Web Cache could not create the XML element or attribute.

Action: Check the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. Restart OracleAS Web Cache if necessary.

WXE-11726 Cannot set XML attribute '%s' for element '%s'.

Severity: error

Cause: OracleAS Web Cache could not set the XML attribute value.

Action: Check the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. Restart OracleAS Web Cache if necessary.

WXE-11727 Unexpected/unsupported argument '%s' in function '%s'.

Severity: error

Cause: The invalidation message specified an unsupported name and value pair for <SYSTEMINFO ... />

Action: See the OracleAS Web Cache documentation for the possible values allowed for <SYSTEMINFO ... />

WXE-11728 Cluster error: Peer cache '%d' returns bad response.

Severity: error

Cause: The invalidation response from a peer cache was not parsed.

Action: Check the network connection between current cache and its peer.

WXE-11729 Invalidation message contains conflicting HOST values: '%s' and '%s'.

Severity: warning

Cause: The invalidation message contained conflicting HOST values in the URIPREFIX and the HOST attributes.

Action: Correct the host information in the invalidation message.

WXE-11730 Invalidation message from provider cache with IP '%s' port '%d' is dropped.

Severity: notification

Cause: The invalidation message propagated from the specified provider cache is either outdated or invalid. Invalidation is discarded.

Action: No action required.

WXE-11731 Normal request is from an unknown OracleAS Web Cache: IP '%s' port '%s'.

Severity: warning

Cause: The invalidation message was propagated from an unknown cache. Invalidation is discarded.

Action: No action required.

WXE-11732 Invalidation contains host name '%s' which does not match the IP '%s' from which invalidation comes.

Severity: warning

Cause: The invalidation message propagated from a cache provided no host name or the host name in the URIPREFIX or HOST attribute was not allowed for that cache. Invalidation is discarded.

Action: Correct the host information in the invalidation message.

WXE-11733 Invalidation object is ignored due to lack of host information.

Severity: notification

Cause: Invalidation propagated from a cache does not specify a host name in the URIPREFIX or HOST attribute of the message.

Action: Correct the host information in the invalidation message.

WXE-11734 Invalidation sent to subscriber cache with IP '%s' port '%d' has returned with response code: '%s'.

Severity: notification

Cause: The provider cache response was received.

Action: No action required.

WXE-11735 Subscriber cache with IP '%s' port '%d' is removed due to an exceeded failure count. Total subscriber(s): '%d'.

Severity: notification

Cause: Subscriber cache was removed from the internal subscriber list because the invalidation propagated to it has failed too many times.

Action: No action required.

WXE-11737 Invalidation message may be lost from provider cache with IP '%s' port '%d'.

Severity: warning

Cause: The subscriber cache missed an invalidation message from the provider cache. All objects are invalidated.

Action: No action required.

WXE-11738 Provider cache fails in propagating invalidation message to subscriber cache.

Severity: error

Cause: The provider cache failed in propagating the invalidation message to subscriber cache.

Action: Check the configuration file. Restart OracleAS Web Cache if necessary.

WXE-11739 New subscriber OracleAS Web Cache with IP '%s' port '%d' has been established. Total subscriber(s): '%d'.

Severity: notification

Cause: The new subscriber cache was added to the internal subscriber list.

Action: No action required.

WXE-11740 Invalidation message contains too many cookies, headers, or attributes. Maximum allowed is '%d'.

Severity: error

Cause: Invalidation message contained too many cookies, headers, or attributes. Invalidation was not performed.

Action: Rephrase the invalidation message.

WXE-11741 Invalidation message received from OracleAS Web Cache with IP '%s' port '%d', sequence number current: '%d', passed: '%d'.

Severity: notification

Cause: OracleAS Web Cache received a propagated invalidation message.

Action: No action required.

WXE-11742 Invalidation sent from IP address '%s' contains host name '%s', is not allowed from that IP address%s

Severity: warning

Cause: The propagated invalidation message contained an invalid host name in the URIPREFIX or HOST attribute.

Action: Correct the host information in the original invalidation message.

WXE-11743 Asynchronous mode is disabled.

Severity: notification

Cause: OracleAS Web Cache is set not to chunk invalidation processing.

Action: No action required.

WXE-11744 Asynchronous mode is enabled; chunk time is %d milliseconds.

Severity: notification

Cause: OracleAS Web Cache is set to chunk invalidation processing.

Action: No action required.

WXE-11747 Running in "disconnected" mode

Severity: trace

Cause: The <SYSTEMINFO ... /> element of the invalidation message was configured with NAME="WCS_DISCONNECTED_OK VALUE="YES". As a result, the invalidation was performed without waiting for an invalidation response for each invalidation message.

Action: No action required.

WXE-11748 Invalidation with INFO '%s' has returned with status '%s'; number of documents invalidated: '%d'.

Severity: notification

Cause: The result of the invalidation was successful. INFO is the comment specified in the INFO element of the invalidation request. The status can be SUCCESS for successful invalidations, URI NOT CACHEABLE for objects that are not cacheable, or URI NOT FOUND for objects not found in the cache.

Action: No action required.

WXE-11750 Invalid syntax for the value of QUERYSTRING_PARAMETER in invalidation message:'%s'.

Severity: error

Cause: The invalidation message contained invalid syntax in the QUERYSTRING_PARAMETER value.

Action: Correct the error in invalidation message.

WXE-11751 Subscriber cache not inserted into internal subscriber list for itself.

Severity: warning

Cause: The subscriber cache was not inserted into the internal subscriber list for itself. The list for the cache could not contain entries for its own cache.

Action: Check the cache topology to verify that loopback is intended.

WXE-11752 Cannot decode %s with value '%s', therefore decoding is not done.

Severity: warning

Cause: Cannot decode XML value specified. The original value is used.

Action: No action required.

WXE-11753 Invalid host name '%s' specified in invalidation message %s

Severity: error

Cause: Invalid host name was specified in the URIPREFIX or HOST attribute of the invalidation message.

Action: Correct the host information in the invalidation message.

WXE-11755 Default URL size is too small for cache key.

Severity: error

Cause: Default URL size was too small for cache key.

Action: No action required.

WXE-11757 Unsupported OTHER element specified in invalidation message: name='%s', type='%s', value='%s'.

Severity: warning

Cause: Unsupported OTHER element was specified in the invalidation message.

Action: See the OracleAS Web Cache Administrator's Guide for all supported OTHER elements.

WXE-11800 CGI communication error.

Cause: Network I/O error while communicating with CGI application.

Action: No action required.

WXE-11802 Cannot open Service Manager: %s

Severity: alert

Cause: The admin server was unable open the Windows Service Manager.

Action: If the problem persists, contact Oracle Support Services.

WXE-11803 Cannot open Windows Service %s: %s

Severity: alert

Cause: The admin server was unable to open the specified service.

Action: If the problem persists, contact Oracle Support Services.

WXE-11804 Cannot obtain the system status for Windows service %s: %s

Severity: alert

Cause: The admin server was unable to retrieve the status for the specified service.

Action: If the problem persists, contact Oracle Support Services.

WXE-11805 Cannot control service %s: %s

Severity: alert

Cause: The admin server was unable to start or stop the specified Windows service.

Action: If the problem persists, contact Oracle Support Services.

WXE-11806 Cannot stop service %s

Severity: alert

Cause: The admin server failed to stop the specified service.

Action: If the problem persists, contact Oracle Support Services.

WXE-11807 Windows service, %s, stopped

Severity: notification

Cause: The admin server has successfully stopped the specified service.

Action: No action required.

WXE-11809 The admin server could not start the cache server, running in admin-only mode

Severity: alert

Cause: The admin server was unable to start the cache server.

Action: Review the error log file or use the Event Viewer to help determine the cause of the problem.

WXE-11810 Cannot start Auto-Restart. %s does not exist

Severity: alert

Cause: Unable to find the specified Auto-Restart executable.

Action: Restore the Auto-Restart executable, webcachemon, to its proper location, which is the OracleAS Web Cache bin directory.

WXE-11811 Unable to fork a new process for starting Auto-Restart.

Severity: alert

Cause: OracleAS Web Cache was unable to fork a new process.

Action: This is probably a temporary system resource issue. If the problem persists, contact Oracle Support Services.

WXE-11812 Auto-Restart did not start. An error code was returned.

Severity: alert

Cause: The Auto-Restart process failed to start.

Action: There may be associated error messages from the Auto-Restart process indicating why it was unable to start. If there are no other error messages, it may be a system resource problem. For example, the exec() call may have failed. If the problem persists, contact Oracle Support Services.

WXE-11813 Cannot start service %s

Severity: alert

Cause: The admin server failed to start the specified service.

Action: If the problem persists, contact Oracle Support Services.

WXE-11814 Logging info: %s

Severity: error

Cause: An error is logged.

Action: Refer to the logged error details and take the appropriate action.

WXE-11815 The admin server process is unable to determine the OPMN auto-restart setting. Error reading or parsing %s

Severity: warning

Cause: An error occurred while the admin server process was attempting to obtain the restart setting for OracleAS Web Cache in the OPMN XML configuration file, opmn.xml.

Action: If the problem persists, contact Oracle Support Services

WXE-11816 Error while changing the OPMN auto-restart setting for OracleAS Web Cache. Command: %s. Return code: %d. Command output: %s

Severity: warning

Cause: An error occurred while trying to execute the command specified. OracleAS Web Cache uses this command to change the restart setting in the OPMN XML configuration file, opmn.xml.

Action: Execute the command manually.

WXE-11817 Unable to create shared memory

Severity: alert

Cause: Unable to create shared memory.

Action: This error usually occurs as a result of insufficient system resources. If the problem persists, contact Oracle Support Services.

WXE-11901 SSL context creation failed, NZERROR %s

Severity: alert

Cause: SSL library failed to create a context.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11902 SSL configuration fails, NZERROR %s

Severity: warning

Cause: SSL library configuration failed.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11903 SSL set credential fails, NZERROR %s

Severity: warning

Cause: SSL library failed to set credentials.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11904 SSL handshake fails NZERROR %s

Severity: warning

Cause: SSL handshake error occurred.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11907 The server cannot allocate memory while in %s.

Severity: alert

Cause: The system has run out of memory.

Action: Restart the system and OracleAS Web Cache.

WXE-11908 SSL set peerid fails, NZERROR %s

Severity: warning

Cause: SSL library failed to create SSL Session

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11909 getpeername fails during SSL handshake, system error %s

Severity: warning

Cause: Could not determine peer IP Address.

Action: Contact Oracle Support Services.

WXE-11910 failed to normalize Wallet Resource Locator (WRL) %s

Severity: warning

Cause: WRL could not be parsed.

Action: Confirm that the WRL is in the correct format.

WXE-11913 SSL set hardware acceleration fails, NZERROR %s

Severity: warning

Cause: SSL library failed to initialize hardware SSL acceleration.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11914 SSL set thread usage fails, NZERROR %s

Severity: warning

Cause: SSL library failed to set threading model.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11915 SSL engine fails to initialize, NZERROR %s

Severity: warning

Cause: SSL library engine failed to initialize.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11916 Oracle cryptographic toolkit context initialization fails, NZERROR %s

Severity: warning

Cause: SSL library toolkit context failed to initialize.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11917 SSL wallet %s file %s does not exist

Severity: warning

Cause: Wallet file was not found in wallet directory

Action: Check for wallet file ewallet.p12 or ewallet.der in wallet directory

WXE-11918 SSL Wallet %s file %s is not readable

Severity: warning

Cause: Wallet file was not readable by OracleAS Web Cache.

Action: Check the file system permissions on this file.

WXE-11919 SSL wallet autologin file %s does not exist. Wallet does not appear to be autologin wallet.

Severity: warning

Cause: The wallet autologin file cwallet.sso was not found.

Action: Check for wallet file cwallet.sso in wallet directory.

WXE-11920 SSL wallet autologin file %s is not readable. Wallet does not appear to be autologin wallet.

Severity: warning

Cause: The wallet autologin file cwallet.sso was not readable by OracleAS Web Cache.

Action: Check the file system permissions on this file.

WXE-11921 Origin server wallet did not open. Operating without wallet for backend. Only Diffie-Hellman anonymous connections supported to origin servers!

Severity: warning

Cause: Origin server wallet did not open or was not specified.

Action: Without an origin server wallet only Diffie-Hellman SSL Connections can be made.

WXE-11922 %s wallet fails to open at location %s, NZERROR %s, as user %s

Severity: warning

Cause: The wallet could not be opened as the user specified.

Action: Check for the existence of the wallet and make sure autologin was enables as the user specified.

WXE-11923 %s wallet fails to open at location %s, NZERROR %s

Severity: warning

Cause: The wallet could not be opened

Action: Check for the existence of the wallet.

WXE-11924 Oracle wallet fails to open persona, NZERROR %s

Severity: warning

Cause: The SSL library failed to retrieve certificate from wallet.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11925 No wallet configured with SSL, Server Initialization Failed.

Severity: alert

Cause: SSL was configured without specifying a wallet.

Action: Correct the configuration file.

WXE-11926 Failed to set cipher suite in SSL Handshake, NZERROR %d

Severity: warning

Cause: The SSL library failed to set the cipher suite.

Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

WXE-11950 Internal XML parser error. Error code: %d. Error Message: %s

Severity: error

Cause: An internal error occurred while inside the XML parser. OracleAS Web Cache will attempt to log that internal error.

Action: This error usually occurs due to malformed XML. Look up the associated error code in the Oracle XDK documentation.

WXE-11951 invalid value for ESI redirect attribute

Severity: warning

Cause: The value specified for the redirect attribute by the <esi:include> tag was invalid.

Action: Set the value of the redirect attribute value to either "yes" or "no" in the ESI template.

WXE-11960 OracleAS Web Cache is unable to decode the URI passed in: %s

Severity: warning

Cause: URI decoding was unsuccessful, and it will be used as it is.

Action: No action required.

WXE-11962 OracleAS Web Cache is unable to allocate enough memory to parse ESI vars tag string

Severity: error

Cause: There was not sufficient memory for OracleAS Web Cache to parse the string in the ESI vars tag.

Action: Adjust the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11963 OracleAS Web Cache failed to create new ESI fragment request. Template uri: %s

Severity: error

Cause: ESI fragment request could not be generated. This error is generally a result of insufficient memory.

Action: Adjust the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11964 empty variable key in ESI vars tag

Severity: error

Cause: The variable key specified in the ESI template by the ESI vars tag was empty. "key" was missing from $(VARIABLE_NAME{key="value"}).

Action: Correct the format of the ESI vars tag.

WXE-11965 invalid variable name in ESI vars tag

Severity: error

Cause: The variable name specified in the ESI template by the ESI vars tag is not defined.

Action: See the OracleAS Web Cache Administrator's Guide for valid ESI variable names.

WXE-11966 In %s%s, request header failed to be added to the include request.

Severity: error

Cause: There was not sufficient memory for OracleAS Web Cache to include the request, or there was a request header parsing error.

Action: Adjust the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11972 OracleAS Web Cache could not allocate memory for POST body

Severity: error

Cause: There was not sufficient memory for OracleAS Web Cache to generate the POST body in an ESI fragment.

Action: Adjust the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-11973 Site name cannot be resolved.

Severity: error

Cause: Requested site in ESI fragment request could not be resolved.

Action: Make sure that site name in the ESI request is correct.

WXE-11974 Incomplete URI for ESI fragment.

Severity: error

Cause: URI for ESI fragment only had "http://" and was considered incomplete.

Action: Make sure that the URL in the ESI request is complete.

WXE-11975 Corrupted login data in ESI environment metadata block.

Severity: error

Cause: The application delivered data that could not be parsed to OracleAS Web Cache.

Action: Fix the application.

WXE-11976 Duplicate name %s in ESI environment metadata block.

Severity: trace

Cause: The environment block contained multiple name entries.

Action: Remove the duplicate entries. Only the first entry is used.

WXE-11977 Memory allocation failure while initializing login metadata hash table.

Severity: alert

Cause: The OracleAS Web Cache memory manager could not allocate any more memory.

Action: Adjust the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager.

WXE-11978 In ESI template %s%s, failed to add request header value.

Severity: error

Cause: Wrong request-header was specified.

Action: Check the ESI template file and correct the error in request_header attribute.

WXE-11979 In ESI template %s%s, failed to add the request header because value is missing

Severity: error

Cause: Value field in the request-header was missing.

Action: Check the ESI template file and correct the error in the request_header attribute

WXE-11984 OracleAS Web Cache is unable to find the directory mapping to the default ESI fragment page %s.

Severity: alert

Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/docs on UNIX or ORACLE_HOME\webcache\docs directory on Windows.

Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/docs on UNIX or ORACLE_HOME\webcache\docs directory on Windows, and then configure it in the Error Pages of OracleAS Web Cache Manager.

WXE-11985 OracleAS Web Cache is unable to obtain the size of the default ESI fragment page %s.

Severity: alert

Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/docs on UNIX or ORACLE_HOME\webcache\docs directory on Windows.

Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/docs on UNIX or ORACLE_HOME\webcache\docs directory on Windows, and then configure it in the Error Pages of OracleAS Web Cache Manager.

WXE-11986 Default ESI fragment page %s is too large.

Severity: alert

Cause: The default ESI fragment was too large.

Action: Alter the size of the default ESI fragment to less than 32 KB.

WXE-11987 OracleAS Web Cache failed to open the default ESI fragment page %s.

Severity: alert

Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/docs on UNIX or ORACLE_HOME\webcache\docs directory on Windows.

Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/docs on UNIX or ORACLE_HOME\webcache\docs directory on Windows, and then configure it in the Error Pages of OracleAS Web Cache Manager.

WXE-11989 read error while loading default ESI fragment page %s

Severity: alert

Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/docs on UNIX or ORACLE_HOME\webcache\docs directory on Windows.

Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/docs on UNIX or ORACLE_HOME\webcache\docs directory on Windows, and then configure it in the Error Pages of OracleAS Web Cache Manager.

WXE-11997 ESI stack overflow

Severity: error

Cause: Current stack maximum depth was set too low.

Action: Contact Oracle Support Services about how to increase the maximum stack depth.

WXE-11999 PPC: %s %s

WXE-12001 ESI <esi:include> tag nesting in template %s%s is too deep.

Severity: warning

Cause: The fragment <esi:include> depth exceeded the maximum include depth of three levels.

Action: Decrease the depth number in the ESI template, or contact Oracle Support Services to change the maximum <esi:include> depth.

WXE-12002 Origin server busy exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: The origin server was busy and could not accept the new request.

Action: Check the health status of the origin server. If needed, increase the origin server capacity in the Origin Server page of OracleAS Web Cache Manager.

WXE-12003 No connection exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: The cache was unable to connect to the origin server.

Action: Check the health status of the origin server. If needed, increase the origin server capacity in the Origin Server page of OracleAS Web Cache Manager.

WXE-12004 Network timeout exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: The request to origin server timed out during a network connection.

Action: Check the health status of the origin server. If needed, increase the origin server capacity in the Origin Server page of OracleAS Web Cache Manager.

WXE-12005 HTTP Client Error 4xx exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: The origin server returned an HTTP 4xx status code.

Action: Check for errors in the ESI template and fragment files.

WXE-12006 HTTP Server Error 5xx exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: The origin server returned an HTTP 5xx status code.

Action: Check for errors in the ESI template and fragment files. Additionally, check the health status of the origin server.

WXE-12007 Incompatible fragment version exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: The value for the content control directive in the Surrogate-Control response-header was not compatible between the ESI fragment and template.

Action: Correct the error in either the ESI template or fragment file.

WXE-12008 Incorrect response header exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: The response header of the ESI fragment caused an error.

Action: Correct the error in the ESI fragment.

WXE-12009 Incorrect ESI fragment exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: OracleAS Web Cache was unable to parse the ESI fragment.

Action: Correct the error in the ESI fragment.

WXE-12010 Incorrect XML Fragment exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: OracleAS Web Cache was unable to parse the XML fragment.

Action: Correct the error in the XML fragment.

WXE-12011 Generic exception in ESI template %s%s, fragment %s%s

Severity: warning

Cause: A generic ESI exception occurred.

Action: Check the template and fragment, and then correct the error.

WXE-12012 No exception handler is defined in template %s%s:.

Severity: error

Cause: An uncaught ESI exception was detected. An error page is returned.

Action: Correct the syntax error in the ESI template.

WXE-12013 No resolved virtual host mapping was found for template.

Severity: trace

Cause: A ESI template contained an unresolved virtual host mapping.

Action: No action required.

WXE-12082 OracleAS Web Cache cannot parse ESI due to insufficient memory

Severity: error

Cause: OracleAS Web Cache ran out of memory while parsing ESI.

Action: Adjust the maximum cache size in the Resource Limits page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-12083 ESI parser internal error at line %d: %s

Severity: error

Cause: An ESI tag closed too early or there was an internal error of the ESI parser.

Action: For any syntax errors, correct the ESI syntax. For any non-syntax related error, contact Oracle Support Services.

WXE-12085 ESI syntax error. Bad exception type at line %d.

Severity: error

Cause: An invalid token was encountered.

Action: Correct the error at the specified location in the ESI template.

WXE-12086 ESI syntax error. Unrecognized keyword %s is at line %d.

Severity: error

Cause: An invalid token was encountered.

Action: Correct the error at the specified location in the ESI template.

WXE-12087 Bad Location response header in ESI fragment response

Severity: error

Cause: A redirection response contained an invalid Location header.

Action: Make sure that the application Web server sends a valid Location header.

WXE-12088 ESI syntax error. The src attribute is missing at line %d.

Severity: error

Cause: The src attribute is required for the <esi:include> and <esi:environment> tags.

Action: Correct the error at the specified location in the ESI template.

WXE-12089 Syntax error. The name attribute is missing at line %d.

Severity: error

Cause: Name is required in environment/inline/req_header. The name attribute is required for the <esi:inline> tag, <esi:environment> tag, and the request_header element.

Action: Include the name attribute at the specified location in the ESI template.

WXE-12090 ESI syntax error. Bad attribute value appears at line %d.

Severity: error

Cause: An invalid or empty value string was found.

Action: Correct the error at the specified location in the ESI template.

WXE-12091 ESI syntax error. Multiple ESI <esi:environment> tags appear in a single template at line %d

Severity: error

Cause: Multiple <esi:environment> tags in a single ESI template are not allowed.

Action: Configure the ESI template with one <esi:environment> tag.

WXE-12092 ESI Syntax error. Multiple request_body elements appear at line %d.

Severity: error

Cause: Multiple request_body elements are not allowed in <esi:include> and <esi:environment> tags.

Action: Correct the error at the specified location in the ESI template.

WXE-12093 ESI syntax error. The max-age attribute is incorrectly formatted at line %d.

Severity: error

Cause: The max-age attribute is not in the format of: max-age="expiration_time[+removal_time]"

Action: Correct the error at the specified location in the ESI template.

WXE-12094 ESI syntax error. String length exceeds maximum at line %d.

Severity: error

Cause: The string length exceeded the maximum limit.

Action: Contact Oracle Support to change the string length limit.

WXE-12095 ESI syntax error. A variable requires a key at line %d.

Severity: error

Cause: The specified variable requires a format of $(VARIABLE_NAME{key}).

Action: Include a key in the variable at the specified location in the ESI template.

WXE-12096 ESI syntax error. The POST request method requires an request_body at line %d.

Severity: error

Cause: The specified POST fragment did not have a request_body element.

Action: Include the request_body element at the specified location in the ESI template.

WXE-12097 ESI syntax error. The position of the <esi:environment> tag at line %d is invalid.

Severity: error

Cause: The <esi:environment> did not appear before any <esi:include> tags in the syntax. To use the custom variables specified by the <esi:environment> tag with other ESI tags, the <esi:environment> must be included before other <esi:include> tags.

Action: Correct the error at the specified location in the ESI template.

WXE-12098 ESI syntax error. The value of the fetchable attribute at line %d is invalid.

Severity: error

Cause: A value of yes or no are the only possible values for the fetchable attribute.

Action: Change the value to either yes or no at the specified location in the ESI template.

WXE-12099 ESI syntax error. The same attribute appears multiple times in an ESI element at line %d.

Severity: error

Cause: An attribute can appear only once within an ESI element.

Action: Correct the error at the specified location in ESI document.

WXE-12100 Exhausted process memory. Exiting process.

Severity: alert

Cause: Memory usage is greater than the process' system memory allocation.

Action: Reduce the maximum cache size limit or increase the operating system's memory limit for the OracleAS Web Cache process, if possible.

WXE-12200 Cache memory allocation for the cluster configuration block failed.

Severity: error

Cause: Memory allocation failed.

Action: No action required.

WXE-12201 Cache memory allocation for the cluster member table failed.

Severity: error

Cause: Memory allocation failed.

Action: No action required.

WXE-12202 Cluster member DNS lookup problem

Severity: trace

Cause: Could not resolve the IP address from the cluster member's host name.

Action: Check the Clustering page of OracleAS Web Cache Manager to see if the host name is correctly listed.

WXE-12203 Cluster member number %s owner slot allocation %s:%s

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12204 Add cluster member number %s

Severity: notification

Cause: Normal notification behavior.

Action: No action required.

WXE-12205 Remove cluster member number %s

Severity: notification

Cause: Normal notification behavior.

Action: No action required.

WXE-12206 Cluster member number %s already marked alive

Severity: warning

Cause: The local cache tried to add the specified cluster member, but it was already marked as alive.

Action: No action required.

WXE-12207 Cluster member number %s already marked dead

Severity: warning

Cause: The local cache tried to remove the specified cluster member, but it was already marked as dead.

Action: No action required.

WXE-12209 A %s node cluster successfully initialized

Severity: notification

Cause: Normal notification behavior.

Action: No action required.

WXE-12212 Cluster member %s - %s configuration is invalid.

Severity: warning

Cause: The configuration file of the specified cluster member does not match the configuration of the local cache.

Action: Check that all cluster members have the same configuration file.

WXE-12213 Cluster member %s - %s configuration is valid.

Severity: notification

Cause: Normal notification behavior.

Action: No action required.

WXE-12217 Cluster member count %s is larger than maximum allowed %s

Severity: error

Cause: There are more than the maximum number of cluster members. There cannot be more than 99 cluster members.

Action: Reduce the number of cluster members by removing some members in the Clustering page of OracleAS Web Cache Manager.

WXE-12400 HTTP request-header exceeds configured maximum individual header size ( %s ). Client IP: %s

Severity: error

Cause: OracleAS Web Cache received an HTTP request with an abnormally large header, indicating a possible denial-of-service attack.

Action: If the problem persists, you may need to increase the maximum individual header size in the Security page of OracleAS Web Cache Manager.

WXE-12401 HTTP request-header exceeds configured maximum combined header size. Client IP: %s

Severity: error

Cause: OracleAS Web Cache received an HTTP request with an abnormally large header, indicating a possible denial-of-service attack.

Action: If the problem persists, you may need to increase the maximum combined header size in the Security page of OracleAS Web Cache Manager.

WXE-12402 HTTP response-header parsing error: %s.

Severity: error

Cause: An HTTP response from the origin server contained a malformed header or a individual header value that was illegal or unexpected.

Action: No action required.

WXE-12403 HTTP response-header parsing error: %s ( %s ).

Severity: error

Cause: An HTTP response from the origin server contained a malformed header or a individual header value that was illegal or unexpected.

Action: No action required.

WXE-12404 The number of search keys exceeds the maximum limit of search keys in the Surrogate-Key response-header.

Severity: warning

Cause: The number of search keys in the Surrogate-Key response-header exceeded the allowed maximum of 20.

Action: Revise the Surrogate-Key response-header with 20 or fewer search keys.

WXE-12405 Illegal time format in HTTP response-header.

Severity: warning

Cause: HTTP response-header contains an illegal time format.

Action: No action required.

WXE-12406 Unexpected EOF while reading HTTP response-header.

Severity: error

Cause: Connection prematurely closed by origin server.

Action: No action required.

WXE-12408 Unexpectedly large HTTP response-header.

Severity: warning

Cause: An unexpectedly large response-header was received from the origin server, indicating a possible performance problem.

Action: Contact Oracle Support Services.

WXE-12409 Timeout while reading HTTP response.

Severity: error

Cause: No timely response received from the origin server, indicating that the origin server is down.

Action: Start origin server, if it is not running.

WXE-12410 Error while reading HTTP response ( SSL error %d ).

Severity: error

Cause: OracleAS Web Cache encountered an SSL read error.

Action: If the problem persists, contact Oracle Support Services.

WXE-12411 HTTP request-header parsing error - illegal token value syntax. Client IP: %s

Severity: error

Cause: An HTTP request from a browser contained a malformed header line - it contained a token value with either an unpaired parenthesis ( ( or ) ) or an unpaired double-quote (").

Action: No action required.

WXE-12412 HTTP request-header parsing error - malformed request line. Client IP: %s

Severity: error

Cause: An HTTP request from a browser contained a malformed request line - it contained either an unknown method name or an illegal version string.

Action: No action required.

WXE-12413 Unable to get Oracle name of ESI template character set ( %s ).

Severity: notification

Cause: A recoverable internal error occurred while doing character set conversion.

Action: No action required.

WXE-12414 Unable to get Oracle name of ESI fragment character set ( %s ).

Severity: notification

Cause: A recoverable internal error occurred while doing character set conversion.

Action: No action required.

WXE-12415 Unable to do character set conversion.

Severity: warning

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support Services.

WXE-12416 NLS library failure while doing character set conversion.

Severity: warning

Cause: Internal error. A system/library call has unexpectedly failed.

Action: If the problem persists, contact Oracle Support Services.

WXE-12417 HTTP request-header parsing error - no header name. Client IP: %s

Severity: error

Cause: An HTTP request from a browser contained a malformed header line - the header name delimiting colon (':') was not present.

Action: No action required.

WXE-12419 Dump of invalid HTTP request-header line

Severity: error

Cause: Any of the causes associated with errors 12411, 12412 and 12417.

Action: No action required.

WXE-12700 Site %s did not match any defined sites, resulting in no End User Performance Monitoring for URI

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12701 Site %s matched one of the defined sites for which End User Performance Monitoring is ON.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12702 Site %s matched a defined site with End User Performance Monitoring OFF, resulting in no End User Performance Monitoring for URI

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12703 No matching End User Performance Monitoring rule found for site %s, resulting in End User Performance Monitoring for URI.

Severity: trace

Cause: Normal trace behavior.

Action: No action required

WXE-12704 There are no End User Performance Monitoring rules defined for site %s, resulting in End User Performance Monitoring for URI.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12705 Matching End User Performance Monitoring REGEXP rule found regexp:%s and the rule is %s

Severity: trace

Cause: Normal trace behavior. Matching End User Performance Monitoring rule found. The rule determines whether or not to monitor End User Performance for the URI.

Action: No action required.

WXE-12706 Matching End User Performance Monitoring SUBSTRING rule found. substring:%s and the rule is %s

Severity: trace

Cause: Normal trace behavior. Matching End User Performance Monitoring rule found. The rule determines whether or not to monitor End User Performance for the URI.

Action: No action required.

WXE-12712 OEMPERFFILE can only be set to an .html file.

Severity: error

Cause: The file specified by OEMPERFFILE must be an .html file, but it was not.

Action: Contact Oracle Support Services for help in specifying the correct OEMPERFFILE.

WXE-12713 OEMPERFFILE cannot be parsed. Use the following format: <SCRIPT SRC="%schronos_JavaScript_filename"></SCRIPT> and restart OracleAS Web Cache.

Severity: error

Cause: OEMPERFFILE could not be parsed.

Action: Use the following format for the value of OEMPERFFILE: <SCRIPT SRC="%schronos_JavaScript_filename"></SCRIPT>. Then, restart OracleAS Web Cache.

WXE-12714 Invalid string specified for OEMPERFFILE.

Severity: error

Cause: The file name specified by OEMPERFFILE is an invalid string.

Action: Contact Oracle Support Services for help in specifying the correct OEMPERFFILE.

WXE-12715 OEMPERFFILE contains an invalid path separator.

Severity: error

Cause: The file name specified for OEMPERFFILE contains an invalid path separator.

Action: Correct the file name specified for OEMPERFFILE.

WXE-12716 End-User Performance Monitoring is enabled.

Severity: notification

Cause: Normal notification behavior. End-User Performance Monitoring is enabled. The event is written to the log file.

Action: No action required.

WXE-12800 OracleAS Web Cache failed to read the configuration file. Dynamic changes have not been applied.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12801 Dynamic Changes Applied Successfully

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12802 The cache server cannot dynamically mark the origin servers as running because they are not responding. Other selected dynamic changes are applied.

Severity: trace

Cause: The origin servers were not responding. The cache server disregarded this dynamic change, but applied other dynamic changes.

Action: No action required.

WXE-12803 Dynamic Changes Not Applied

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12804 Event Log rolled over.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12805 Access Log %s rolled over.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12806 Non Existent or NULL Access Log specified in rollover request

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12807 Event log not rolled over because the rollover file already exists.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-12808 Access log not rolled over because the rollover file already exists.

Severity: trace

Cause: Normal trace behavior.

Action: No action required.

WXE-13001 Virtual Host Map %s has a mixture of HTTP and HTTPS Protocol origin servers. All origin servers for a virtual host map must use the same protocol.

Severity: alert

Cause: The specified virtual host map consists of origin servers with HTTP and HTTPS protocols. A virtual host mapping must consist of origin servers that use either the HTTP protocol exclusively or the HTTPS protocol exclusively.

Action: From the Site Definitions page of OracleAS Web Cache Manager, correct the mapping. Then, restart OracleAS Web Cache.

WXE-13002 Maximum allowed incoming connections are %u

Severity: notification

Cause: Normal notification behavior indicating the maximum number of concurrent connections which will be accepted.

Action: No action required.

WXE-13003 Configuration error. Stopping admin or cache server.

Severity: alert

Cause: The admin or cache server was unable to parse or read its configuration information.

Action: Review any other error messages to determine the cause of the problem.

WXE-13004 Invalid PPC tree frame array size: %s, setting to %u

Severity: warning

Cause: The partial-page caching (PPC) tree frame array size was invalid. OracleAS Web Cache set the size to the value indicated.

Action: OracleAS Web Cache set the tree frame array size to a valid size. Contact Oracle Support Services if you want to set it to another value. The value must be a positive integer.

WXE-13050 Multiple access logs use the same file name: %s

Severity: alert

Cause: Multiple access logs were configured to use the same output file name. The output file name cannot be shared by multiple access logs.

Action: Ensure that the ACCESSLOG element in the webcache.xml file has a unique FILENAME attribute.

WXE-13074 A session caching rule refers to an invalid session name: %s

Severity: alert

Cause: The session caching rule specifies a session ID which is not defined. This error usually occurs if webcache.xml has been edited manually instead of by using OracleAS Web Cache Manager.

Action: Edit webcache.xml and set the session ID to a valid session definition.

WXE-13075 A session binding rule refers to an invalid session name: %s

Severity: alert

Cause: A session binding rule specified a session ID which was not defined. This error usually occurs if webcache.xml has been edited manually instead of by using OracleAS Web Cache Manager.

Action: Edit webcache.xml and correct the session definition for the specified session ID.

WXE-13076 A caching rule refers to an invalid expiration rule: %s

Severity: alert

Cause: One of the caching rules contained the specified expiration rule. That expiration rule was invalid. This error usually occurs if webcache.xml has been edited manually instead of by using OracleAS Web Cache Manager.

Action: Edit webcache.xml and find the specified expiration rule and replace it with a valid expiration rule.

WXE-13077 A caching rule refers to an invalid multi-version cookie rule: %s

Severity: alert

Cause: One of the caching rules contained the specified invalid multi-version cookie rule. This error usually occurs if webcache.xml has been edited manually instead of by using OracleAS Web Cache Manager.

Action: Edit webcache.xml and find the multi-version cookie rule listed in the error message. Replace the rule with a valid one.

WXE-13078 A caching rule refers to an invalid session rule: %s

Severity: alert

Cause: One of the caching rules contained the specified invalid session rule. This error usually occurs if webcache.xml has been edited manually instead of by using OracleAS Web Cache Manager.

Action: Edit webcache.xml and find the specified session rule. Replace the rule with a valid one.

WXE-13079 No matching CACHE element found in webcache.xml for current hostname (%s) and ORACLE_HOME (%s)

Severity: alert

Cause: Unable to find a CACHE element for this cache.

Action: Check that the hostname and ORACLE_HOME printed in the error message match the expected values and check the CACHE elements in webcache.xml for one which is defined for these values.

WXE-13080 No NAME attribute is specified in ROLLOVER element under ACCESSLOGSTYLES

Severity: alert

Cause: Unable to find a NAME attribute in ROLLOVER element for access logs. The ROLLOVER element for access logs must have a NAME attribute.

Action: Edit webcache.xml and find the ROLLOVER element under ACCESSLOGSTYLES which doesn't have NAME attribute. Add the NAME attribute to the ROLLOVER element.

WXE-13101 Invalid ppcVarSize: %s

Severity: alert

Cause: The partial-page caching ppcVarSize specified was invalid.

Action: Contact Oracle Support Services to set it to a proper value. The value must be a positive integer.

WXE-13102 Invalid PPC include max depth: %s, setting to %u

Severity: warning

Cause: The partial-page caching (PPC) include max depth setting was invalid. OracleAS Web Cache set it to the value indicated.

Action: OracleAS Web Cache set the include max depth to a valid size. Contact Oracle Support Services to set it to another value. The value must be a positive integer.

WXE-13103 Invalid PPC stack size: %s, setting to %u

Severity: warning

Cause: The partial-page caching (PPC) default stack size is invalid. OracleAS Web Cache set it to the value indicated.

Action: OracleAS Web Cache set the default stack size to a valid size. Contact Oracle Support Services to set it to another value. The value must be a positive integer.

WXE-13106 Log file rollover schedule refers to an invalid TIME value for the HOURLY frequency: %u

Severity: alert

Cause: Time value specified for the HOURLY frequency was invalid.

Action: TIME must be set to a nonzero positive integer value less than 60.

WXE-13107 Log file rollover schedule refers to an invalid TIME value for the DAILY frequency: %u

Severity: alert

Cause: Time value specified for the DAILY frequency was invalid.

Action: For DAILY rollover, the time format is "hhmm", where hh ranges from 0 to 23 and mm ranges from 0 to 59.

WXE-13108 Log file rollover schedule refers to an invalid TIME value for the WEEKLY frequency: %u

Severity: alert

Cause: Time value specified for the WEEKLY frequency was invalid.

Action: For WEEKLY rollover, the time format is "dhhmm", where "d" ranges from 0 to 6, "hh" ranges from 0 to 23 and mm ranges from 0 to 59.

WXE-13109 XML parsing error in %s. Error code %u: %s

Severity: alert

Cause: The specified XML file did not match the DTD for the file.

Action: See the related Oracle XML library error message for more details.

WXE-13110 XML parser initialization error. Error code: %u

Severity: alert

Cause: Unable to initialize the XML parser.

Action: If the problem persists, contact Oracle Support Services.

WXE-13111 XML parsing failed for file: %s. Error Code: %u

Severity: alert

Cause: An XML parsing error occurred when parsing the specified file.

Action: Review associated error messages for more information about the problem.

WXE-13112 XML parsing failed. Error Code: %u

Severity: error

Cause: Failed to parse an XML message.

Action: Review associated error messages for more information about the problem.

WXE-13113 Syntax error in %s. Exception: "%s" in attribute "%s" having value "%s" in element %s

Severity: error

Cause: An exception occurred while parsing the specified file.

Action: Edit the specified file to make it a valid XML document.

WXE-13114 A root directory mapping must be specified before all other mappings

Severity: error

Cause: This error may have occurred if the internal configuration has been changed.

Action: Contact Oracle Support Services.

WXE-13115 Out of memory error while scanning document root

Severity: alert

Cause: The process ran out of memory while scanning for documents in the document root.

Action: If the problem persists, contact Oracle Support Services.

WXE-13116 An error occurred scanning the directory %s

Severity: error

Cause: OracleAS Web Cache was unable to get the contents of the specified directory.

Action: If the problem persists, contact Oracle Support Services.

WXE-13117 Failed to add MIME type extension to pool: %s

Severity: error

Cause: An error occurred while processing the MIME type extensions settings.

Action: If the problem persists, contact Oracle Support Services.

WXE-13118 Out of memory error while initializing MIME type information

Severity: error

Cause: An error occurred while processing the MIME type extensions settings.

Action: If the problem persists, contact Oracle Support Services.

WXE-13119 Duplicate origin server hosts specified for host %s port %s.

Severity: error

Cause: There are duplicate entries in the HOST section of the webcache.xml file.

Action: Remove the duplicate entries from webcache.xml.

WXE-13120 CACHEWITH and CACHEWITHOUT cannot both have the value "NO" in a session caching policy for session %s.

Severity: error

Cause: The session caching policy has a value of "NO" for both CACHEWITH and CACHEWITHOUT in webcache.xml.

Action: Set at least one of them to be "YES", or remove the policy.

WXE-13121 The caching rule for %s contains more than one multi-version cookie policy based on the same cookie: %s.

Severity: error

Cause: More than one multi-version cookie policy is associated for the same cookie with one caching rule.

Action: Remove the extra policies from the caching rule.

WXE-13122 The caching rule for %s contains more than one session-caching policy based on the same session: %s.

Severity: error

Cause: More than one session caching policy is associated for the same session with one caching rule.

Action: Remove extra policies from the caching rule.

WXE-13123 Site name %s:%s exceeds maximum individual header limit.

Severity: error

Cause: The site name was set to more than the maximum single header limit as defined in the security section.

Action: Increase the maximum individual header size limit in the Security page or change the site name in the Site Definitions page of OracleAS Web Cache Manager, so that the site name and port number string together is less than the specified limit.

WXE-13124 Alias name %s:%s exceeds maximum individual header limit %d.

Severity: error

Cause: The alias name was set to more than maximum individual header limit as defined in the security section.

Action: Increase the maximum individual header size limit in the Security page or change the alias name in the Site Definitions page of OracleAS Web Cache Manager, so that the alias name and port number string together is less than the specified limit.

WXE-13125 internal.xml does not have CALYPSOINTERNALPARAMS element.

Severity: error

Cause: Unable to find CALYPSOINTERNALPARAMS element in internal.xml.

Action: Check whether internal.xml conforms to internal.dtd.

WXE-13126 No default site defined. From OracleAS Web Cache Manager, change one site from Site Definitions to be default site.

Severity: alert

Cause: All the sites defined in the configuration are set "NO" for the default site option.

Action: From OracleAS Web Cache Manager, make the changes to the site definitions so that at least one site is the default site.

WXE-13200 Access logging was skipped as the request had not been parsed properly.

Severity: error

Cause: Due to an error in request parsing, access logging could not be completed.

Action: None

WXE-13212 Access log file %s could not be opened.

Severity: alert

Cause: Access log file could not be opened.

Action: Check the status of access log file. For example, check the permission of the file.

WXE-13213 Invalid access log field name: %s

Severity: alert

Cause: An invalid access log field is specified in the configuration file webcache.xml.

Action: Set valid access log field name.

WXE-13215 I/O Error when writing access Log buffer to file. error number: %d

Severity: alert

Cause: I/O error happened when OracleAS Web Cache tried to write to the access log file.

Action: Check the status of access log file. For example, see if the disk is full.

WXE-13250 Search key configuration error

Severity: alert

Cause: Invalid OracleAS Web Cache configuration for search key.

Action: Contact Oracle Support Services.

WXE-13251 The HTML file for End-User Monitoring was not found

Severity: alert

Cause: End-User Monitoring configuration error.

Action: Disable End-User Monitoring or restore the HTML file that is missing. If the problem persists, contact Oracle Support Services.

WXE-13252 On Demand Log File Rollover for file %s was not successful. File %s could not be created.

Severity: warning

Cause: The rollover file could not be created.

Action: Check the file permissions.

WXE-13301 A failure occurred with DNS lookups. No more DNS lookups will occur.

Severity: warning

Cause: The DNS server might be unavailable.

Action: Check the DNS configuration on the local machine.

WXE-13302 failed to open directory ( %s )

Severity: warning

Cause: Directory could not be opened because it does not exist or the access permissions are incorrect.

Action: Check the configuration and the permissions for accessing the directory.

WXE-13305 failed to assign port %s, bind() error = %s

Severity: alert

Cause: The selected port is being used by another application.

Action: Change the port to an unused port.

WXE-13306 Failed to configure resources for port %s, listen() error = %s.

Severity: alert

Cause: System listen function call failed.

Action: Restart OracleAS Web Cache. If the problem persists, contact Oracle Support Services.

WXE-13307 Failed to allocate resources for port %s, WSASocket() error = %s

Severity: alert

Cause: Socket creation failed.

Action: Restart OracleAS Web Cache. If the problem persists, check open file descriptors and contact Oracle Support Services.

WXE-13310 Problem opening file %s (Access Denied).

Severity: warning

Cause: The file could not be opened because of an access problem.

Action: Fix the file permissions so that the user running webcached can access the file.

WXE-13312 Problem opening file %s (File Already Exists).

Severity: warning

Cause: The file could not be created because it already exists.

Action: Choose a file name that does not exist.

WXE-13313 Problem opening file %s (Invalid Drive).

Severity: warning

Cause: The file could not be opened because the drive name is invalid.

Action: Correct the file specification.

WXE-13314 Problem opening file %s (Invalid Name).

Severity: warning

Cause: The file could not be opened because the file name is invalid.

Action: Correct the file specification.

WXE-13315 Problem opening file %s (Too Many Open Files).

Severity: warning

Cause: The file could not be opened because there are too many open files in the system.

Action: Close other files or programs and restart OracleAS Web Cache.

WXE-13316 Problem opening file %s (File Not Found).

Severity: warning

Cause: The file could not be opened because the file could not be found.

Action: Correct the file specification.

WXE-13317 Problem opening file %s (Sharing violation).

Severity: warning

Cause: The file could not be opened because there has been a sharing violation.

Action: Close the file through other applications that are accessing it.

WXE-13318 Problem opening file %s (Is a directory).

Severity: warning

Cause: The file could not be opened because it is directory.

Action: Correct the file specification.

WXE-13350 Error during network receive, system error %s

Severity: trace

Cause: There was system error during the networking receive.

Action: No action required.

WXE-13351 Timeout during network receive, socket number %s

Severity: error

Cause: There was timeout during the networking receive.

Action: No action required.

WXE-13365 Error during network send, system error %s

Severity: trace

Cause: There was system error during the networking send.

Action: No action required.

WXE-13366 Timeout during network send, socket number %s

Severity: trace

Cause: There was timeout during the networking send.

Action: No action required.

WXE-13380 Error during SSL handshake, system error %s

Severity: error

Cause: There was system error during the SSL handshake.

Action: No action required.

WXE-13381 Timeout during SSL handshake, socket number %s

Severity: error

Cause: There was timeout during the SSL handshake.

Action: No action required.

WXE-13382 File %s cannot be opened.

Severity: error

Cause: The specified file could not be opened.

Action: Evaluate why the specified file cannot be opened. The file may not be located in the correct directory or permissions on the file may be incorrect. Correct the problem.

WXE-13383 Unable to initialize DNS lookups

Severity: warning

Cause: Cannot use DNS for TCP/IP host resolution.

Action: No required action.

WXE-13400 parsing error of <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> at offset %d

Severity: error

Cause: An invalid token was encountered in the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags.

Action: Correct the syntax of the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags at the specified location in the document.

WXE-14002 Error while sending the request to origin server

Severity: warning

Cause: The request to the origin server failed.

Action: Ensure that the origin server is running.

WXE-14003 Error while receiving response from the origin server

Severity: warning

Cause: OracleAS Web Cache was unable to receive a response from the origin server.

Action: Ensure that the origin server is running.

WXE-14004 HTTP status code error

Severity: warning

Cause: The origin server returned a non-HTTP status code.

Action: Check the origin server to determine what application is sending the response.

WXE-14005 Content-Type buffer is too small

Severity: warning

Cause: The buffer pool memory was not sufficient.

Action: Adjust the maximum individual header size limit in the Security page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

WXE-14006 SSL handshake with origin server fails.

Severity: warning

Cause: The SSL handshake between OracleAS Web Cache and the origin server failed.

Action: Check certificate configuration on the origin server.

WXE-14007 Connect request terminates.

Severity: warning

Cause: The connection request to the origin server was terminated.

Action: If the problem persists, contact Oracle Support Services.

WXE-14008 Create request fails.

Severity: warning

Cause: OracleAS Web Cache failed to create a request to the origin server.

Action: If the problem persists, contact Oracle Support Services.

WXE-14009 Header operation fails.

Severity: warning

Cause: OracleAS Web Cache could not write to the HTTP response header from the origin server. This occurs if the OracleAS Web Cache computer is experiencing a system memory problem.

Action: If the problem persists, contact Oracle Support Services.

WXE-14010 Invalid authentication credentials for proxy server

Severity: warning

Cause: The user name and password for the proxy server failed.

Action: Correct the user name and password in the Origin Servers page of OracleAS Web Cache Manager.

WXE-14011 Proxy tunnel authentication required

Severity: warning

Cause: The user name and password for the proxy server failed.

Action: Correct the user name and password in the Origin Servers page of OracleAS Web Cache Manager.

WXE-14012 Bad response from proxy tunnel

Severity: warning

Cause: The proxy tunnel response was incorrect.

Action: Check the proxy server configuration and setup.

WXE-14013 Send request to origin server times out.

Severity: warning

Cause: The request to the origin server exceeded the network timeout limit.

Action: If the problem persists, adjust the network timeout between OracleAS Web Cache and the origin server in the Network Timeouts page of OracleAS Web Cache Manager.

WXE-14014 Receive request from origin server times out.

Severity: warning

Cause: The response from the origin server exceeded the network timeout limit.

Action: If the problem persists, adjust the network timeout between OracleAS Web Cache and the origin server in the Network Timeouts page of OracleAS Web Cache Manager.

WXE-14015 Browser terminates connection; the request to the origin server is terminated.

Severity: warning

Cause: The browser terminated its connection. As a result, OracleAS Web Cache terminated its connection to the origin server.

Action: No action required.

WXE-14016 Connection to origin server fails.

Severity: warning

Cause: The origin server is down.

Action: Check the origin server.

WXE-14017 Connection to origin server times out.

Severity: warning

Cause: The connection to the origin server exceeded the network timeout limit.

Action: If the problem persists, adjust the network timeout between OracleAS Web Cache and the origin server in the Network Timeouts page of OracleAS Web Cache Manager.

WXE-14018 Socket creation fails for origin server.

Severity: warning

Cause: The OracleAS Web Cache computer has run short of system resources.

Action: If the problem persists, increase the Maximum Incoming Connections setting in the Resource Limits page of OracleAS Web Cache Manager.

WXE-14019 Dynamic origin server DNS failure

Severity: warning

Cause: The DNS lookup for the ESI provider site failed, because either the site was down or does not exist.

Action: Ensure that the ESI provider site is operational. If it is, check the site configuration in the Site-to-Server Mapping page of OracleAS Web Cache Manager.

WXE-14020 Origin server rejects queue entry.

Severity: warning

Cause: The queue to the origin server was full, resulting in the new request not being accepted.

Action: If the problem persists, increase the capacity for the origin server in the Origin Servers page of OracleAS Web Cache Manager.

WXE-14021 Origin server drops request.

Severity: warning

Cause: OracleAS Web Cache was unable to forward the request to the origin server, because the origin server reached its capacity and queue limit.

Action: If the problem persists, increase the capacity for the origin server in the Origin Servers page of OracleAS Web Cache Manager.

WXE-14022 Load balancing and failover functionality fails.

Severity: warning

Cause: All of the origin servers were down. OracleAS Web Cache will continue to poll the origin server until they are back online.

Action: Check the state of the origin servers.

WXE-14023 No origin server is running.

Severity: warning

Cause: All communication to the origin servers has failed. OracleAS Web Cache will continue to poll the origin server until they are back online.

Action: Check the state of the origin servers.

WXE-14024 Dynamic origin server is not allowed for request.

Severity: warning

Cause: The request was for a virtual host site. DNS discovery of origin servers is only permitted for ESI provider sites.

Action: Check the site configuration in the Site Definitions and Site-to-Server Mapping page of OracleAS Web Cache Manager.

WXE-14025 Dynamic connection to origin server fails.

Severity: warning

Cause: OracleAS Web Cache received the DNS lookup result for the ESI provider site, but was unable to connect to the site.

Action: Check that the ESI provider site is operational.

WXE-14027 Connection request times out.

Severity: warning

Cause: The connection between OracleAS Web Cache and the origin server timed out.

Action: No action required.

WXE-14028 incomplete header

Severity: warning

Cause: The HTTP response from the origin server did not contain a properly formatted HTTP header.

Action: Check the application sending the response.

WXE-14029 invalid header

Severity: warning

Cause: The HTTP header response from the origin server contained an invalid field.

Action: Check the application sending the response.

WXE-14032 Buffer finished before is found.

Severity: warning

Cause: The response from the origin server was not properly formatted.

Action: If the problem persists, check the application sending the response.

WXE-14036 time overflow

Severity: warning

Cause: Invalid time string from Origin Server.

Action: Check the Origin Server configuration setting.

WXE-14037 illegal time format

Severity: warning

Cause: The creation time received from the origin server was for a time in the future.

Action: Check the application sending the response.

WXE-14039 HTTP response not found

Severity: warning

Cause: An HTTP response from the origin server was not found.

Action: Check the application sending the response.

WXE-14041 invalid format

Severity: warning

Cause: The response contained an invalid time format or inversion of an integer.

Action: No action required.

WXE-20101 Open socket fd=%d exceeded FDArr_Size %d.

Severity: alert

Cause: Potential file descriptor leakage.

Action: Contact Oracle Support Services.

WXE-20150 Failure in scheduling asynchronous task: %s.

Severity: alert

Cause: Potential memory shortage. Note: This is for all asynchronous functions.

Action: Contact Oracle Support Services.


Go to previous page Go to next page
Oracle
Copyright © 2002, 2003 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index