17 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
OracleAS Web Cache rates each message by severity level:
-
notification
: A normal activity, for example, the start up or shut down of the cache server or an event log rollover.
-
trace
: Information that helps trace the activity of OracleAS Web Cache. These messages are particularly helpful in debugging caching rules. Messages with a severity level of trace are written to the event log file only when a Verbosity of Trace is selected in the event log configuration.
-
warning
: An event which is abnormal or potentially a sign of a problem, but OracleAS Web Cache will continue to operate without any lack of service. For example, a request header included a malformed header, but OracleAS Web Cache interpreted it in some way and continued processing.
-
error
: An event which can cause lack of service only within the request/response transaction. For example, OracleAS Web Cache cannot continue the transaction because of malformed request.
-
alert
: An event which can affect an OracleAS Web Cache instance and can cause lack of service in a subsequent request/response transaction. For example, the origin server is not reachable or sufficient memory is unavailable. In many cases, the cache server will be shut down when an alert event is encountered.
In addition, OracleAS Web Cache provides messages, that are not included in this appendix, with severity levels of debug or internal error:
Messages that Reference Network Security Messages (NZE)
Several SSL-related errors are reported with NZE errors in the event log. Oracle Database Error Messages lists these errors in full, and "Resolving Common NZE Errors" describes the most commons NZE errors reported to the event log.
Message Listing
-
00800 Auto-Restart started successfully
-
notification
-
Cause: The Auto-Restart process has successfully completed its initialization.
-
Action: No action required.
-
08000 Auto-Restart process terminating.
-
alert
-
Cause: This error usually occurred as a result of insufficient system resources.
-
Action: If the problem persists, contact Oracle Support.
-
08001 Failed to start the cache server. Auto-Restart process terminating.
-
alert
-
Cause: This error usually occurred as a result of insufficient system resources.
-
Action: If the problem persists, contact Oracle Support.
-
08002 Failed to find a Web Cache listening port that does not require SSL client-side certificates. Auto-Restart pinging is disabled.
-
warning
-
Cause: Auto-Restart does not support the use of client-side certificates. If all OracleAS 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.
-
08500 Cache server not responding on port %d.
-
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.
-
08501 Timeout occurred communicating with the cache server.
-
error
-
Cause: The cache server was either in an unstable state or slow responding to queries.
-
Action: From the Auto-Restart page of Oracle Enterprise Manager or OracleAS Cache Manager, check the ping timeout interval and increase it if necessary.
-
08502 Lost connection with the cache server.
-
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.
-
08503 Operating system level error in %s() (%d): %s.
-
error
-
Cause: The specified system call returned the specified error.
-
Action: No action required.
-
08504 %u consecutive errors pinging the cache server.
-
notification
-
Cause: The Auto-Restart process received the specified number of failures when attempting to reach the cache server.
-
Action: No action required.
-
08505 %u consecutive error(s) pinging the cache server. %d error(s) required for restart.
-
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.
-
08506 Unable to retrieve the cache server process ID from %s. Stopping the Auto-Restart process.
-
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.
-
08507 Cache server process not running.
-
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.
-
08508 Restarting the cache server.
-
alert
-
Cause: See accompanying error messages for more information.
-
Action: No action required.
-
08509 Starting the cache server.
-
alert
-
Cause: See accompanying error messages for more information.
-
Action: No action required.
-
08510 SSL set hardware acceleration failed. NZE-%d.
-
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.
-
08511 SSL Set Thread Usage Failed. NZE-%d.
-
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.
-
08512 SSL Engine Failed to Initialize. NZE-%d.
-
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.
-
09000 Process %d exit(%d) at %d:%s [%s]
-
alert
-
Cause: The Web Cache process shutdown.
-
Action: No action required.
-
09001 An error occurred while disabling core file creation.
-
warning
-
Cause: The system/library call to disable core file creation returned an error.
-
Action: If the problem persists, contact Oracle Support.
-
09200 An error occurred while trying to create a background process.
-
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.
-
09403 Maximum number of file/socket descriptors set to %s.
-
notification
-
Cause: The specified number of file descriptors is set for use by OracleAS Web Cache.
-
Action: No action required.
-
09521 OracleAS Web Cache fails to find user ( %s ) in /etc/passwd.
-
alert
-
Cause: The specified user was not found in the password file.
-
Action: Add user to the password file.
-
09522 OracleAS Web Cache fails to find group ( %s ) in /etc/group.
-
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 Security page of Oracle Enterprise Manager or the Process Identity page of OracleAS Web Cache Manager.
-
09523 Invalid user ID ( %s ).
-
alert
-
Cause: The specified user ID was invalid.
-
Action: Correct the user ID in the Security page of Oracle Enterprise Manager or Process Identity page of OracleAS Web Cache Manager.
-
09524 Invalid group ID ( %s )
-
alert
-
Cause: The specified group ID was invalid.
-
Action: Correct the group ID in the Security page of Oracle Enterprise Manager or Process Identity page of OracleAS Web Cache Manager.
-
09525 Permission denied when setting user ID ( %s ).
-
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.
-
09526 Permission denied when setting group ID ( %s ).
-
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.
-
09534 Unexpected File I/O Error ( %s ) when opening file %s.
-
alert
-
Cause: Could not open specified file.
-
Action: Review specified error to determine the problem on your system.
-
09570 Directory not found when unlinking file %s
-
notification
-
Cause: The directory was not found.
-
Action: Verify that OracleAS Web Cache was installed properly. You may need to reinstall OracleAS Web Cache.
-
09571 Too many files open when unlinking file %s.
-
notification
-
Cause: Too many files were open for available system resources.
-
Action: Adjust system resources and restart OracleAS Web Cache.
-
09572 No disk space available when unlinking file %s
-
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.
-
09573 Unexpected File I/O Error ( %s ) when unlinking file %s.
-
notification
-
Cause: There was an unexpected input/output file error.
-
Action: Review the specified error and correct the problem on the system.
-
09574 Permission denied when unlinking file %s.
-
notification
-
Cause: Permission denied on file.
-
Action: Set correct permission on the specified file.
-
09600 SIGTERM caught - program will shut down once all connections are complete.
-
notification
-
Cause: Normal notification behavior. Shutdown event written to the log file.
-
Action: No action required.
-
09601 SIGUSR1 caught - program will reread configuration files after all connections are complete.
-
notification
-
Cause: Normal notification behavior. Configuration file reread event written to the log file.
-
Action: No action required.
-
09602 All configuration files have been reread.
-
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.
-
09603 There was an error rereading the configuration files. The program is exiting.
-
alert
-
Cause: Invalid OracleAS Web Cache configuration files.
-
Action: Correct the OracleAS Web Cache configuration files and restart OracleAS Web Cache.
-
09604 Could not increase the number of file/socket descriptors to %s.
-
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.
-
09605 Cannot create OPMN shutdown thread. Continuing with startup.
-
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.
-
09606 Cannot create OPMN shutdown event. Continuing with startup.
-
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.
-
09607 The admin server started successfully.
-
notification
-
Cause: The OracleAS Web Cache admin server process started successfully.
-
Action: No action required.
-
09608 The cache server process started successfully.
-
notification
-
Cause: The OracleAS Web Cache server process has started successfully.
-
Action: No action required.
-
09609 The server process could not initialize.
-
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.
-
09610 The server is exiting.
-
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.
-
09611 The server could not start the service thread.
-
alert
-
Cause: The server process could not start the Service thread.
-
Action: Determine why OracleAS Web Cache cannot start a thread on your system.
-
09612 OracleAS Web Cache %s, %s
-
notification
-
Cause: Normal notification behavior. The OracleAS Web Cache version number was written to the log file.
-
Action: No action required.
-
09614 The following OracleAS Web Cache internal files are pre-populated to the cache: %s
-
notification
-
Cause: The specified OracleAS Web Cache internal files are loaded into the cache.
-
Action: No required action.
-
09700 Unable to initialize NLS. Error %d
-
alert
-
Cause: A system/library call has unexpectedly failed.
-
Action: If the problem persists, contact Oracle Support.
-
09701 Unable to initialize NLS global structure.
-
alert
-
Cause: A system/library call has unexpectedly failed.
-
Action: If the problem persists, contact Oracle Support.
-
09702 NLS boot file not found or missing; using default.
-
warning
-
Cause: A system/library call has unexpectedly failed.
-
Action: If the problem persists, contact Oracle Support.
-
09703 Stop Issued. The program will shut down after all accepted requests are served, or a timeout occurs.
-
notification
-
Cause: Stop was issued.
-
Action: OracleAS Web Cache will be stopped.
-
09704 Abort Issued. The program will shut down immediately.
-
notification
-
Cause: Abort was issued.
-
Action: OracleAS Web Cache will be stopped immediately.
-
09705 Error accessing the Oracle Notification Service library, %s: %s
-
alert
-
Cause: An error occurred when attempting to open or access functions in the Oracle Notification Service (ONS) library.
-
Action: 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."
-
09706 Ignoring unrecognized option: %s
-
alert
-
Cause: An alert was logged.
-
Action: Refer to the logged alert details and take the appropriate action.
-
09707 Failed to start the server.
-
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: 1. Reduce the capacity of cluster members in the Cluster Members and Properties page of Oracle Enterprise Manager or the Clustering page of OracleAS Web Cache Manager. 2. Ensure the IP address and listening ports of OracleAS Web Cache conflict with existing applications. 3. Check whether OracleAS Web Cache has root privilege to bind to specified ports. You can use the webcache_setuser.sh script to run webcached as root. See section "Running webcached with Root Privilege" in the OracleAS Web Cache Administrator's Guide.
-
09709 OracleAS Web Cache fails HTTP initialization.
-
alert
-
Cause: OracleAS Web Cache failed to initialize HTTP.
-
Action: 1. Check the configuration of the access log in the Logging page of Oracle Enterprise Manager or the Access Logs page of OracleAS Web Cache Manager. 2. Check whether OracleAS Web Cache has root privilege to set the process ID. You can use the webcache_setuser.sh script to run webcached as root. See section "Running webcached with Root Privilege" in the OracleAS Web Cache Administrator's Guide. 3. If the problem persists, contact Oracle Support.
-
09710 Cache server fails to initialize.
-
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.
-
09711 Problem loading message file for event log. Exiting.
-
alert
-
Cause: Message file for event log was not correctly loaded.
-
Action: Check the existence and permissions of the file wxeus.msb in $ORACLE_HOME/webcache/mesg/wxeus.msb on UNIX and ORACLE_HOME\webcache\mesg on Windows.
-
09712 Unable to open the Oracle Notification Service library, %s:%s. Searching the library path.
-
warning
-
Cause: An error occurred when attempting to open the Oracle Notification Service (ONS) library.
-
Action: 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 event message 09705.
-
10054 Unable to resume service, UIPI return value is %s.
-
alert
-
Cause: Service could not be resumed.
-
Action: Review the error to determine the problem on your system.
-
10417 MIME Type Extension ( %s ) exceeds current size limit.
-
warning
-
Cause: Unexpected MIME type configured.
-
Action: No action required.
-
10418 Encoding Extension ( %s ) exceeds current size limit.
-
warning
-
Cause: Unexpected encoding type configured.
-
Action: No action required.
-
10419 Language Extension ( %s ) exceeds current size limit.
-
warning
-
Cause: Unexpected language type configured.
-
Action: No action required.
-
10536 You must specify a full path for %s. See %s %s.
-
alert
-
Cause: Failed to specify full path name.
-
Action: Specify a full path name for the file.
-
11058 Stale object updated for %s%s
-
trace
-
Cause: The complete response was successfully received and the cache entry is updated with the new response.
-
Action: No action required.
-
11059 Garbage object updated for %s%s
-
trace
-
Cause: The complete response was successfully received and the cache entry is updated with the new response.
-
Action: No action required.
-
11060 Object update aborted for %s%s.
-
trace
-
Cause: The response will not be used to update the stale or garbage object in the cache because it was determined that it is not cacheable.
-
Action: No action required.
-
11062 <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tag parsing error
-
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.
-
11064 ESI object %s%s parsing error
-
warning
-
Cause: Object contained invalid ESI syntax.
-
Action: Correct the ESI syntax in the source.
-
11077 Cluster member sent invalid configuration error
-
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.
-
11078 Malformed environment object %s%s
-
warning
-
Cause: The syntax of the XML file specified by the ESI environment is incorrect.
-
Action: Check the XML object for possible syntax errors.
-
11083 Proxy server configuration error: %s
-
error
-
Cause: The proxy server was not correctly configured.
-
Action: Check the proxy server configuration in the Origin Servers page of Oracle Enterprise Manager or OracleAS Web Cache Manager and the general configuration of the proxy server itself.
-
11085 Authentication for the remote or subscriber cache is being challenged by a central or provider cache. Retry.
-
trace
-
Cause: Access to the central or provider cache requires authorization.
-
Action: Try accessing the cache again.
-
11088 Following URL is now in cache:
-
trace
-
Cause: The complete response was successfully received and populated into the cache.
-
Action: No action required.
-
11089 Error while sending the entity body to the origin server
-
error
-
Cause: OracleAS Web Cache encountered a bad network connection or the origin server was down.
-
Action: No action required
-
11091 Error while processing ESI for %s%s
-
warning
-
Cause: An error was encountered while ESI processing was done for the response. The page will not be cached.
-
Action: No action required.
-
11092 Object validated for %s%s
-
trace
-
Cause: The cached object was validated by the origin server and its expiration timestamps were updated accordingly.
-
Action: No action required.
-
11093 Content-Length value %d sent by origin server does not match number of bytes received, that is %d bytes for %s%s.
-
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.
-
11095 Update fails because object is no longer cacheable.
-
trace
-
Cause: This request was no longer cacheable.
-
Action: No action required.
-
11110 The maximum cache size is set too low. OracleAS Web Cache failed to initialize.
-
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 for information about the internal.xml file.
-
11111 Based on maximum cache memory limit %s, a cache table is created.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
11118 Duplicate search key %s found in Surrogate-Key response header is discarded.
-
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.
-
11119 The number of search keys changed.
-
warning
-
Cause: The number of search keys has changed for the same cached object.
-
Action: No action required.
-
11128 A duplicate cache insertion is found. Cache insertion fails.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
11136 An error occurs during shutdown. The internal.xml file has been corrupted or moved.
-
alert
-
Cause: The internal.xml file was corrupted or moved during the shutdown operation.
-
Action: Recover internal.xml by copying from internal.xml.bak.
-
11201 OracleAS Web Cache is unable to resolve the IP address of %s. Check your DNS setup.
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
11202 Origin server %s does not use IPv4.
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
11203 OracleAS Web Cache fails to connect to the origin server (id=%d).
-
warning
-
Cause: An origin server is not available.
-
Action: Check the status of the origin server and the network connection.
-
11205 OracleAS Web Cache marked the origin server %s:%u (id=%d) as down and removed all session information bound to it.
-
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.
-
11206 OracleAS Web Cache is unable to start pinging the origin server. rc code=%d
-
alert
-
Cause: There was a potential memory allocation error.
-
Action: Check the configured memory usage in the Resource Limits and Timeouts page of Oracle Enterprise Manager or the Resource Limits page of OracleAS Web Cache Manager.
-
11207 Origin server %s:%u (id=%d) is down; OracleAS Web Cache starts polling for status.
-
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.
-
11208 Cache cluster member %s (id=%d) is down; cache cluster members start polling for status. Ping threshold set at %d.
-
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.
-
11209 Origin server %s:%u (id=%d) is back up; OracleAS Web Cache stops polling and restores origin server.
-
warning
-
Cause: The ping URL to the origin server succeeded.
-
Action: No action required.
-
11210 Cache cluster member %s (id=%d) is up; cache cluster members stop polling and restore it.
-
warning
-
Cause: The ping URL to the cache cluster member succeeded.
-
Action: No action required.
-
11211 All origin servers for site %s are down. Last origin server was (id=%d).
-
warning
-
Cause: All origin servers configured for the site are down.
-
Action: No action required.
-
11212 Cache cluster member %s (id=%d) pinged successfully. %d successful pings so far.
-
warning
-
Cause: An origin server is not available.
-
Action: Check the status of the origin server and the network connection.
-
11220 Session binding routing to origin server %s:%u (id=%d) for site %s
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
11221 The origin server request is queued for site %s and site-to-server mapping %s.
-
trace
-
Cause: The origin server was busy.
-
Action: No action required.
-
11222 The origin server request is dropped due to a full queue for site %s and site pattern %s.
-
trace
-
Cause: The origin server request queue was full.
-
Action: No action required.
-
11223 The origin server request is routed to peer cache cluster member %s (id=%d) for site %s.
-
trace
-
Cause: The request did not support session binding, and the requested object was owned by the peer cache cluster member.
-
Action: No action required.
-
11224 Site %s matches site-to-server mapping %s.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
11225 OracleAS Web Cache cannot find any running origin servers to route the request for site %s.
-
warning
-
Cause: All origin servers are down.
-
Action: No action required.
-
11226 The session binding request is to a busy origin server %s:%u (id=%d) for site %s.
-
trace
-
Cause: The session binding request was to a server was that was busy.
-
Action: No action required.
-
11227 Request is routed to origin server %s:%u using load balancing.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
11228 No defined origin server can serve this request for site %s. The request is dropped.
-
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.
-
11229 This ESI fragment request is forwarded to a dynamic origin server for ESI provider site %s.
-
trace
-
Cause: The request was for an ESI fragment without a matching site-to-server mapping.
-
Action: No action required.
-
11240 Origin server %s:%u (id=%d) has %d connections timed out or closed for other reasons.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
11250 ESI include fragment protocol does not match origin server protocol: Origin Server Protocol=%s URL=%s%s%s
-
warning
-
Cause: The protocol used in the src attribute does not match the protocol specified in the Sites page of Oracle Enterprise Manager or Site-to-Server Mapping page of OracleAS Web Cache Manager. OracleAS Web Cache used the protocol configured for the origin server in the Sites or Site-to-Server Mapping page.
-
Action: Correct the protocol in the template for the fragment.
-
11260 Session binding cookie %s with cookie value %s exceeds limit %d.
-
warning
-
Cause: The value of the session binding cookie exceeded the allowed length limit for the Internal-Tracking session binding mechanism. limit in OracleAS Web Cache.
-
Action: Consider using another session binding mechanism, such as Cookie-Based, or consider modifying the application so that the length of the session binding cookie value does not exceed the limit.
-
11261 Session binding query string parameter name %s with value %s exceeds limit of %d bytes.
-
warning
-
Cause: The value of the session binding query string parameter exceeded the allowed length limit for the Internal-Tracking session binding mechanism.
-
Action: Consider using another session binding mechanism, such as Cookie-Based, or consider modifying the application so that the length of the session binding cookie value does not exceed the limit.
-
11290 DNS cache miss. Scheduling DNS task for host name %s
-
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.
-
11291 DNS lookup task scheduling fails for host %s.
-
alert
-
Cause: Asynchronous task scheduling failed.
-
Action: Check the log of corresponding asynchronous task scheduling.
-
11292 DNS lookup succeeds for host %s.
-
trace
-
Cause: The DNS cache miss and lookup succeeded.
-
Action: No action required.
-
11293 OracleAS Web Cache fails to connect to dynamic origin server for ESI provider site and again performs a DNS lookup for host %s.
-
trace
-
Cause: There was a possible stale DNS cache entry.
-
Action: No action required.
-
11294 OracleAS Web Cache fails to connect to a dynamic origin server for ESI provider site with fresh DNS lookup result for host %s.
-
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.
-
11295 OracleAS Web Cache failed in DNS lookup for host %s.
-
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.
-
11296 Dynamic origin server name %s is too long.
-
error
-
Cause: Dynamic origin server name specified for an ESI fragment is longer than 255 characters.
-
Action: Check the host name that appears in src attribute of <esi:include> tag.
-
11297 Cached DNS look up result for host %s is used.
-
trace
-
Cause: Cached DNS look up result was used to establish a connection to a dynamic origin server.
-
Action: No action required.
-
11300 The attempt to create an entry in the cache failed due to low memory.
-
alert
-
Cause: Memory low during insertion.
-
Action: No action required.
-
11303 Request method is not GET nor POST nor PUT; tunneling.
-
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.
-
11304 Cache miss request.
-
trace
-
Cause: The cache did not have a object matching the request.
-
Action: No action required.
-
11306 Request is for a non-cacheable object, forwarding request to the backend.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
11308 Request may not be cacheable according to caching rule.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
11311 OracleAS Web Cache generates a HTTP 200 OK status code.
-
trace
-
Cause: The request completed successfully.
-
Action: No action required.
-
11312 invalid Oracle-ECID request header
-
error
-
Cause: OracleAS Web Cache was unable to parse the Oracle-ECID request header.
-
Action: Correct the syntax of the Oracle-ECID request header.
-
11313 The cache server reached the maximum number of allowed incoming connections. Listening is temporarily suspended on port %d.
-
alert
-
Cause: The cache server reached the maximum number of incoming connections specified in the Resource Limits and Timeouts page in Oracle Enterprise Manager or Resource Limits page or OracleAS Web Cache Manager.
-
Action: Try again later. If this message persists, increase the maximum incoming connections in the Resource Limits and Timeouts page of Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
11314 Listening has resumed on port %d.
-
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.
-
11315 OracleAS Web Cache generates a HTTP 202 Accepted status code.
-
trace
-
Cause: The request was accepted.
-
Action: No action required.
-
11316 The request is for an end-user performance monitoring GIF file.
-
trace
-
Cause: Normal activity for end-user performance monitoring.
-
Action: No action required.
-
11317 OracleAS Web Cache generates an HTTP 304 Not-Modified status code.
-
trace
-
Cause: OracleAS Web Cache sent an HTTP 304 Not-Modified status code to the browser.
-
Action: No action required.
-
11321 Connection from browser cannot be established.
-
error
-
Cause: The handshake with the browser failed.
-
Action: No action required.
-
11327 The request contains incorrect content.
-
error
-
Cause: The object request could not be processed because the request contained incorrect or malformed information. Typical reasons are invalid, incomplete or malformed header information. This error can also occur when referencing ESI-only objects from non-ESI requests.
-
Action: Check the event log to determine which information is incorrect.
-
11330 The request prefix %s%s matches an alias for configured site %s.
-
trace
-
Cause: The alias for the site matched the Host request header.
-
Action: No action required.
-
11331 Request matches configured site %s.
-
trace
-
Cause: The Host request header matched the site name.
-
Action: No action required.
-
11332 Failed to rewrite URI from '%s' to '%s' according to rewrite rule '%s'. The original URI will be used.
-
warning
-
Cause: URI rewrite failed. OracleAS Web Cache will use the original URI in subsequent operations without rewriting.
-
Action: Modify URL rewrite rules.
-
11333 URI is rewritten from %s to %s according to rewrite rule %s.
-
trace
-
Cause: URI rewrite was successful.
-
Action: No action required.
-
11334 User-Agent request header %s does not match any rule. OracleAS Web Cache remapped User-Agent to the default value %s.
-
trace
-
Cause: User-Agent request header did not match any rule.
-
Action: Manually modify user-agent rules in the webcache.xml file.
-
11335 User-Agent request header remapped from %s to %s according to mapping rule %s.
-
trace
-
Cause: User-Agent request header matched a rule.
-
Action: No action required.
-
11336 The request fails authorization check.
-
error
-
Cause: The request was not processed due to insufficient privileges or authorization rejection.
-
Action: Make sure you are authorized to perform the invalidation operation.
-
11337 Administration service unavailable. Try again later.
-
warning
-
Cause: There were too many administration requests.
-
Action: Ensure that only one user is the administrator user.
-
11338 URL is in the cache
-
trace
-
Cause: There was a matching entry in the cache for this request.
-
Action: No action required.
-
11339 OracleAS Web Cache determined the request might be cacheable based on existing cache policy.
-
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.
-
11340 A new entry in the cache is created.
-
trace
-
Cause: OracleAS Web Cache created an entry in the cache for this request.
-
Action: No action required.
-
11342 OracleAS Web Cache determined the request might not be cacheable based on existing cache policy.
-
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.
-
11343 The requested site does not have a matching origin server mapping. A bad request error will be returned.
-
error
-
Cause: There was no matching site-to-server mapping for this non-ESI-fragment request.
-
Action: No action required.
-
11344 Returning a freshly cached object.
-
trace
-
Cause: The cached object will be returned because it is still fresh.
-
Action: No action required.
-
11345 The cached object is stale and this request will be served stale.
-
trace
-
Cause: The cached object is stale and OracleAS Web Cache decided to serve the stale copy to the request.
-
Action: No action required.
-
11346 The cached object is stale and an origin server will be contacted for a fresh copy.
-
trace
-
Cause: Because the cached object is stale, OracleAS Web Cache fetched a new version of the object to update the cache and satisfy this request with the new response.
-
Action: No action required.
-
11347 The cached object is garbage.
-
trace
-
Cause: The cached object is in garbage state, meaning that it could not be used to serve to the client.
-
Action: No action required.
-
11348 There is already another pending request for the same object being forwarded to the origin server for a fresh copy. This request will wait for the fresh copy.
-
trace
-
Cause: The cached object is in garbage state, and there is another request for the same object 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.
-
11349 The request will be forwarded to the origin server to obtain a fresh copy of the object.
-
trace
-
Cause: The cached object 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 object to update the cache and satisfy this request with the new response.
-
Action: No action required.
-
11350 The request contains no site information in the URL or Host header. The configuration of the default site %s will be used.
-
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.
-
11351 The complete site name is: %s
-
trace
-
Cause: The complete site name was resolved based on the configuration.
-
Action: No action required.
-
11352 There is no matching defined site or aliases in the configuration for this request.
-
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.
-
11354 Out of memory while processing the request. A service unavailable response is returned to the client. Client IP: %s
-
alert
-
Cause: OracleAS Web Cache failed to obtain enough memory while processing the request.
-
Action: Adjust the maximum cache size in the Resource Limits and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager.
-
11355 Single request header length exceeds configured maximum. A forbidden error response is returned to the client. Client IP: %s
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
11356 Total request header length exceeds configured maximum. A forbidden error response is returned to the client. Client IP: %s
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
11357 Failed to resolve the requested site name. A bad host error response is returned to the client.
-
error
-
Cause: The request did not contain enough information about the site name.
-
Action: No action required.
-
11358 Failed client certificate check. A forbidden error response is returned.
-
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.
-
11359 Host header missing in HTTP/1.1 request. A bad host error response is returned.
-
error
-
Cause: The request was an HTTP/1.1 request, but is missing the required Host header.
-
Action: No action required.
-
11360 Error processing the Transfer-Encoding header in the request. A bad request error response is returned.
-
error
-
Cause: An error was encountered while processing the Transfer-Encoding header in the request.
-
Action: No action required.
-
11361 Transfer-Encoding specified in the request is not supported. An HTTP not implemented error response is returned.
-
error
-
Cause: OracleAS Web Cache only supports chunked encoding. Other types transfer encoding are not supported.
-
Action: No action required.
-
11362 Malformed request. A bad request error response is returned. Client IP: %s
-
error
-
Cause: The request was malformed.
-
Action: No action required.
-
11363 Out of memory while processing the request. The request is dropped.
-
error
-
Cause: OracleAS Web Cache failed to obtain enough memory while processing the request.
-
Action: Adjust the maximum cache size in the Resource Limits and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager.
-
11364 Network error response is returned.
-
error
-
Cause: A network error was encountered while processing the request.
-
Action: Check other error messages related to this request.
-
11365 Server busy response is returned.
-
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.
-
11366 A client connection to listening port %d is dropped.
-
warning
-
Cause: A connection failure was encountered between OracleAS Web Cache and the client, so the request could not be completed.
-
Action: No action required.
-
11367 No matching origin server can be found for the requested site. A bad host error response is returned
-
error
-
Cause: The requested site did not have any matching origin servers in the configuration.
-
Action: Modify the Sites page of Oracle Enterprise Manager or Site-to-Server Mapping page of OracleAS Web Cache Manager.
-
11368 ESI exception error response is returned.
-
error
-
Cause: An ESI exception was encountered while processing the request.
-
Action: Check other error messages related to this request.
-
11369 The request method is not supported. An HTTP not implemented error response is returned.
-
error
-
Cause: The request specified an unsupported method.
-
Action: No action required.
-
11370 A chunk-encoded request entity body contains a chunk that exceeds %u bytes. A bad request error response is returned. Client IP: %s
-
error
-
Cause: This chunk-encoded request contained a chunk that exceeded the DOCHEADERBUFFERSIZE setting in internal.xml
-
Action: Consider increasing DOCHEADERBUFFERSIZE.
-
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
-
error
-
Cause: The request is malformed.
-
Action: none
-
11372 Aborting origin server request
-
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.
-
11373 This request %s is not being enabled with end-user performance monitoring.
-
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.
-
11376 The cached object is stale and this request will be served stale. However origin server is already being contacted for the fresh copy by some other request
-
trace
-
Cause: The cached object is stale and OracleAS Web Cache decided to serve the stale copy to the request. The origin server was already contacted for the fresh copy by some other request
-
Action: No action required.
-
11377 Aborting receiving request entity body because origin server connection has been aborted
-
trace
-
Cause: An error occurred while sending the request entity body to an origin server. The origin server connection was aborted. Because of this, OracleAS Web Cache is aborting the request received from the client.
-
Action: No action required.
-
11379 The request is using global site configuration.
-
trace
-
Cause: OracleAS Web Cache used global site configuration for this request.
-
Action: No action required.
-
11380 Request URL path prefix %s is re-written to %s based on site definition.
-
trace
-
Cause: URL path prefix was re-written based on the site configuration.
-
Action: No action required.
-
11381 A request is sent for a forbidden operation.
-
error
-
Cause: The request was attempted to be performed on an IP address for which the operation is forbidden.
-
Action: Check the IP address to ensure the correct target platform was specified.
-
11382 The URL for the statistics monitoring request is not valid.
-
error
-
Cause: The incorrect URL was used for the statistics monitoring request.
-
Action: Check the URL.
-
11385 The request fails because the service is unavailable.
-
error
-
Cause: The request was not processed because the service at the specified IP address was not available.
-
Action: Make the sure service is available prior to initiating the invalidation request.
-
11386 The request fails because the portal service is unavailable.
-
error
-
Cause: The request was not processed because the service at the specified IP address was not available.
-
Action: Make sure the service is available prior to initiating the invalidation request.
-
11387 The request fails due to a gateway timeout.
-
error
-
Cause: The request was not be processed due to a gateway timeout.
-
Action: Make sure the gateway is active and available for processing requests.
-
11389 The request fails due to unsupported ESI operation.
-
error
-
Cause: The request was not processed because no clients on the path of request can provide sufficient ESI processing capability.
-
Action: Check the offending ESI tag for correctness or possible typographical errors.
-
11390 The ECID %s overrides the temporary ECID %s.
-
notification
-
Cause: The ECID generated internally by OracleAS Web Cache was overridden by the new ECID discovered in the incoming Oracle-ECID request header. From now on, events logged within the request/response context will be displayed with the new ECID instead of the temporary ECID.
-
Action: No action required.
-
11391 Detailed information about ECID %s is in the next line.
-
notification
-
Cause: Additional information about the request represented by the ECID was acquired and will be printed in the next line in the event log.
-
Action: No action required.
-
11392 The object is in the cache, but the inactivity timeout cookie must be updated.
-
trace
-
Cause: The cached object will be returned to the client, but the inactivity timeout cookie must first be updated.
-
Action: No action required.
-
11393 The central cache or provider cache has challenged the remote or subscriber cache for identity information.
-
trace
-
Cause: The central cache or provider cache requested content from its parent cache. Before receiving content, it must register itself as an OracleAS Web Cache to establish a hierarchical relationship.
-
Action: No action required.
-
11394 The invalidation request is redundant.
-
trace
-
Cause: The invalidation request was not processed because the request was redundant with a previous requests. This error can occur in cache hierarchies.
-
Action: No action required.
-
11397 request failed due to insufficient memory
-
alert
-
Cause: The object request failed due to insufficient memory necessary to process all of the objects.
-
Action: Increase the size of the pagefile.
-
11398 A client connection to listening port %d is dropped at the end of keep-alive session.
-
trace
-
Cause: A connection between OracleAS Web Cache and the client was terminated, marking the end of the keep-alive session.
-
Action: No action required.
-
11399 The port number in the Host header %s is replaced with the port number of the connection %d.
-
trace
-
Cause: As a work around for an known Internet Explorer problem, the port number in the Host header was ignored and port number of the actual connection was used to determine the site instead.
-
Action: No action required.
-
11400 non-200 OK HTTP status code response code of %d
-
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.
-
11403 begin cacheability decision for following url:
-
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.
-
11404 Time %s in the Last-Modified header is after the current time. The cache is using the current time instead.
-
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, and make sure the machine where OracleAS Web Cache is running on has its clock in-sync with the clock of the application Web server.
-
11406 URL matches no-cache rule "%s".
-
trace
-
Cause: The request URL matched a non-cacheable caching rule.
-
Action: No action required.
-
11407 URL matches caching rule "%s".
-
trace
-
Cause: The request URL matched a cacheable caching rule.
-
Action: No action required.
-
11408 URL does not match any caching rule.
-
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.
-
11409 HTTP POST request body length %d exceeds maximum cacheable limit. %d.
-
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.
-
11410 Response contains cookie "%s=%s", which is not present in the request.
-
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.
-
11411 Response contains cookie "%s=%s", which does not match the same cookie value "%s" in the request.
-
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.
-
11412 The Surrogate-Control header conflicts with an existing caching rule. Cached objects associated with the previous rule will be marked for removal from the cache.
-
trace
-
Cause: The Surrogate-Control header in the response contained control directives that were in conflict with an existing caching rule. This will cause OracleAS Web Cache to mark all existing objects in the cache that were associated with the previous rule for removal.
-
Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
-
11413 The HTTP request method is not GET, or the URL contains query string parameters. The request is not cacheable.
-
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.
-
11414 Initial cache key is composed:
-
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.
-
11415 Final cache key is composed:
-
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.
-
11416 The response is considered not cacheable due to the lack of caching directives.
-
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.
-
11417 URL is not cacheable based on its HTTP headers.
-
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.
-
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.
-
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.
-
11419 The Surrogate-Control header contains a nonzero max-age=%d+%d control directive, indicating that the response is cacheable.
-
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.
-
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.
-
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.
-
11421 The response contains Etag and X-Oracle-Cache headers, indicating that the response is cacheable with validation.
-
trace
-
Cause: The response contained Etag and X-Oracle-Cache headers. As a result, OracleAS Web Cache considered it to be cacheable with validation.
-
Action: No action required.
-
11422 The Surrogate-Control header contains the vary control directive, overriding configuration.
-
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.
-
11423 OracleAS Web Cache ran out of memory while creating caching rule according to the vary control directive of the Surrogate-Control header.
-
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 and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager.
-
11424 The request contains session %s, which makes it non-cacheable based on the existing caching rule.
-
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.
-
11425 The request does not contain session %s, which makes it non-cacheable based on the existing caching rule.
-
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.
-
11426 The request does not contain cookie %s, which makes it non-cacheable based on the existing caching rule.
-
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.
-
11427 The request does not contain HTTP request header %s, which makes it non-cacheable based on the existing caching rule.
-
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.
-
11428 The X-Oracle-Expires header contains TTL of %d sec, indicating that the response is cacheable.
-
trace
-
Cause: The response contained an X-Oracle-Expires header with a nonzero TTL value. As a result, OracleAS Web Cache considered it to be cacheable.
-
Action: No action required.
-
11429 The response contains Etag header and zero value TTL in X-Oracle-Expires header, indicating that the response is cacheable with validation.
-
trace
-
Cause: The response contained an X-Oracle-Expires header with a zero value TTL and an Etag header. As a result, OracleAS Web Cache considered it to be cacheable with validation.
-
Action: No action required.
-
11430 The response contains zero value TTL in X-Oracle-Expires header with no Etag header, indicating that the response is non-cacheable.
-
trace
-
Cause: The response contained an X-Oracle-Expires header with a zero value TTL. As a result, OracleAS Web Cache considered it to be not cacheable.
-
Action: No action required.
-
11431 In absence of any overriding headers in the response, the response is not cacheable based on the existing caching rule.
-
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.
-
11432 The HTTP response headers indicate that the response is cacheable. %s
-
trace
-
Cause: The response contained HTTP headers that indicate it is cacheable.
-
Action: No action required.
-
11433 An existing NCM entry states object is too large to be cacheable .
-
trace
-
Cause: The response body size was possibly greater than the maximum cacheable object size.
-
Action: If this is not the desired behavior, increase the maximum cached object size value in the Resource Limits and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager.
-
11434 The ESI include or inline tag for this fragment contains reference TTL=%d+%d, making the fragment cacheable.
-
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.
-
11442 The response could not be parsed.
-
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.
-
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.
-
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.
-
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.
-
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.
-
11445 Following URL will not be cached:
-
trace
-
Cause: The final cacheability decision for this response is not cacheable.
-
Action: No action required.
-
11446 URL which will be cached is:
-
trace
-
Cause: The final cacheability decision for this response is cacheable.
-
Action: No action required.
-
11447 Request URL matches a dynamic caching rule.
-
trace
-
Cause: The request URL matched a dynamic caching rule.
-
Action: No action required caching rules.
-
11448 URL matches disabled caching rule "%s".
-
trace
-
Cause: The request URL matched a disabled caching rule; thus, the rule is ignored.
-
Action: No action required.
-
11449 The response is too large to be cached.
-
trace
-
Cause: The response size is larger than the configured maximum size of a single cached object.
-
Action: Check the configured Maximum Size of a Single Cached Object in the Resource Limits and Timeouts page of Oracle Enterprise Manager or the Maximum Cached Object Size in the Resource Limits page of OracleAS Web Cache Manager.
-
11450 Object is cached because it does not exceed allowed size for an object.
-
trace
-
Cause: The object was cacheable because its response was within the configured maximum object size. Previously, the object was uncacheable because it exceeded the limit.
-
Action: No action required.
-
11451 Update fails because object is no longer cacheable.
-
trace
-
Cause: This request was no longer cacheable.
-
Action: No action required.
-
11452 Update fails; OracleAS Web Cache fetches response as a cache miss.
-
trace
-
Cause: An update of the object failed. OracleAS Web Cache processes request as a cache miss
-
Action: No action required.
-
11453 A new cache policy is created based on the Surrogate-Control header.
-
trace
-
Cause: The caching properties specified in the Surrogate-Control header conflicts with the existing cache policy, therefore OracleAS Web Cache created a new policy to be used for future requests.
-
Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
-
11454 The compression setting derived from the Surrogate-Control header or the absence of the header conflicts with the existing setting. Cached objects associated with the previous setting will be marked for removal from the cache.
-
trace
-
Cause: The response contains a compression setting either explicitly through the Surrogate-Control header or implicitly through the absence of it that was in conflict with an existing compression setting. This will cause OracleAS Web Cache to mark all existing objects in the cache that were associated with the previous setting for removal.
-
Action: If this is not the intended behavior, then check the application logic, as well as the configured caching rule.
-
11501 While getting detailed memory statistics, pointer swapped while filling HTML
-
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.
-
11502 Unable to create or open file %s for write. Cache contents not written.
-
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.
-
11503 Abnormal statistics value of %s was detected. Value 0 was recorded.
-
alert
-
Cause: The statistics value that was returned was an negative value. This problem is typically caused by a OracleAS Web Cache server that has been active for a long period of time. OracleAS Web Cache automatically reset the value.
-
Action: No action required.
-
11504 Client IP checking for the statistics message fails. Access denied.
-
error
-
Cause: OracleAS Web Cache allows statistics requests to be sent from configured trusted hosts or trusted subnets. The current statistics request message was not sent from an IP address that belongs to a trusted host or subnet.
-
Action: Add the IP address for the computer as trusted host in the Security page of Oracle Enterprise Manager or the Security page of OracleAS Web Cache Manager.
-
11505 The number of statistics monitoring requests exceeds queue limit.
-
alert
-
Cause: The number of statistics monitoring requests exceeded the request queue limit.
-
Action: Try the request at a later time.
-
11700 Client IP checking for the invalidation message fails. Access denied.
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
11701 Authentication failed. Invalid username or password.
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
11702 The invalidation request contains an empty request body.
-
error
-
Cause: The invalidation request contained an empty request body.
-
Action: Resend the invalidation request with a request body.
-
11703 Invalidation request specifies a wrong URL.
-
error
-
Cause: The invalidation message carried a wrong request URL.
-
Action: No action required.
-
11704 Invalidation message contains XML parsing errors.
-
error
-
Cause: The invalidation message contained invalid XML.
-
Action: Correct the XML errors in the invalidation message.
-
11705 Invalid validity level '%s' is requested.
-
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.
-
11706 %d object(s) matching prefix '%s' are invalidated.
-
notification
-
Cause: Invalidation of objects was successful.
-
Action: No action required.
-
11707 Object with URL '%s' is successfully invalidated.
-
notification
-
Cause: Invalidation was successful.
-
Action: No action required.
-
11708 Object with URL '%s' is not cacheable. Invalidation is not done.
-
notification
-
Cause: The URL was not a cacheable object. Invalidation is not performed for non-cacheable objects.
-
Action: No action required.
-
11710 Object with URL '%s' not in the cache. Invalidation is not performed.
-
notification
-
Cause: The object was not in the cache. Invalidation is not performed for non-cacheable objects.
-
Action: No action required.
-
11711 OracleAS Web Cache cannot compose key pattern for requested URL '%s'.
-
error
-
Cause: OracleAS Web Cache could not compose a key pattern for requested URL expression.
-
Action: Correct the URL expression in the invalidation message.
-
11712 Invalidation message contains unrecognized cookies.
-
error
-
Cause: The invalidation message contained nonexistent cookies.
-
Action: Correct the cookie name specified in the invalidation message.
-
11713 Invalid regular expression found in invalidation message. %s
-
error
-
Cause: The invalidation message contained an invalid regular expression that could not be compiled.
-
Action: Correct the regular expression in the invalidation message.
-
11715 Regular expression matching error. Error number: %d
-
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 the error number for syntax error description.
-
11716 Invalidation XML message cannot be parsed.
-
error
-
Cause: Invalidation XML message could not be parsed.
-
Action: No action required.
-
11717 Invalidation XML error found in invalidation message.
-
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".
-
11721 Cannot read value for XML element/attribute: '%s'.
-
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.
-
11722 Invalidation message specifies unknown version: '%s'.
-
error
-
Cause: The invalidation message specified an unknown version.
-
Action: Correct the invalidation message to use version "WCS-1.1" or "WCS-1.0".
-
11723 Value of XML string '%s' too long. Actual length: %d, max length allowed: %d.
-
error
-
Cause: The XML string in the invalidation message exceeded the allowed length limit.
-
Action: Correct the XML in the invalidation message.
-
11724 URL path prefix does not end with '/': '%s'.
-
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.
-
11725 Cannot create XML element/attribute: '%s'.
-
error
-
Cause: OracleAS Web Cache could not create the XML element or attribute.
-
Action: Check the maximum cache size in the Resource Limits and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager. Restart OracleAS Web Cache if necessary.
-
11726 Cannot set XML attribute '%s' for element '%s'.
-
error
-
Cause: OracleAS Web Cache could not set the XML attribute value.
-
Action: Check the maximum cache size in the Resource Limits and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager. Restart OracleAS Web Cache if necessary.
-
11727 Unexpected/unsupported argument '%s' in function '%s'.
-
error
-
Cause: The invalidation message specified an unsupported name and value pair for <SYSTEMINFO ... />
-
Action: See chapter "Sending Invalidation Requests" in the OracleAS Web Cache Administrator's Guide for the possible values allowed for <SYSTEMINFO ... />.
-
11728 Cluster error: Peer cache '%d' returns bad response.
-
error
-
Cause: The invalidation response from a peer cache was not parsed.
-
Action: Check the network connection between current cache and its peer.
-
11729 Invalidation message contains conflicting HOST values: '%s' and '%s'.
-
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.
-
11730 Invalidation message from provider cache with IP '%s' port '%d' is dropped.
-
warning
-
Cause: The invalidation message propagated from the specified provider cache is either outdated or invalid. Invalidation is discarded.
-
Action: No action required.
-
11731 Normal request is from an unknown OracleAS Web Cache: IP '%s' port '%s'.
-
warning
-
Cause: The invalidation message was propagated from an unknown cache. Invalidation is discarded.
-
Action: No action required.
-
11732 Invalidation contains host name '%s' which does not match the IP '%s' from which invalidation comes.
-
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.
-
11733 Invalidation object is ignored due to lack of host information.
-
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.
-
11734 Invalidation sent to subscriber cache with IP '%s' port '%d' has returned with response code: '%s'.
-
notification
-
Cause: The provider cache response was received.
-
Action: No action required.
-
11735 Subscriber cache with IP '%s' port '%d' is removed due to an exceeded failure count. Total subscriber(s): '%d'.
-
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.
-
11737 Invalidation message may be lost from provider cache with IP '%s' port '%d'.
-
warning
-
Cause: The subscriber cache missed an invalidation message from the provider cache. All objects are invalidated.
-
Action: No action required.
-
11738 Provider cache fails in propagating invalidation message to subscriber cache.
-
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.
-
11739 New subscriber OracleAS Web Cache with IP '%s' port '%d' has been established. Total subscriber(s): '%d'.
-
notification
-
Cause: The new subscriber cache was added to the internal subscriber list.
-
Action: No action required.
-
11740 Invalidation message contains too many cookies, headers, or attributes. Maximum allowed is '%d'.
-
error
-
Cause: Invalidation message contained too many cookies, headers, or attributes. Invalidation was not performed.
-
Action: Rephrase the invalidation message.
-
11741 Invalidation message received from OracleAS Web Cache with IP '%s' port '%d', sequence number current: '%d', passed: '%d'.
-
notification
-
Cause: OracleAS Web Cache received a propagated invalidation message.
-
Action: No action required.
-
11742 Invalidation sent from IP address '%s' contains host name '%s', is not allowed from that IP address%s
-
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.
-
11743 Asynchronous mode is disabled.
-
notification
-
Cause: OracleAS Web Cache is set not to chunk invalidation processing.
-
Action: No action required.
-
11744 Asynchronous mode is enabled; chunk time is %d milliseconds.
-
notification
-
Cause: OracleAS Web Cache is set to chunk invalidation processing.
-
Action: No action required.
-
11747 Running in "disconnected" mode
-
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.
-
11748 Invalidation with INFO '%s' has returned with status '%s'; number of objects invalidated: '%d'.
-
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.
-
11750 Invalid syntax for the value of QUERYSTRING_PARAMETER in invalidation message:'%s'.
-
error
-
Cause: The invalidation message contained invalid syntax in the QUERYSTRING_PARAMETER value.
-
Action: Correct the error in invalidation message.
-
11751 Subscriber cache not inserted into internal subscriber list for itself.
-
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.
-
11752 Cannot decode %s with value '%s', therefore decoding is not done.
-
warning
-
Cause: Cannot decode XML value specified. The original value is used.
-
Action: No action required.
-
11753 Invalid host name '%s' specified in invalidation message %s
-
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.
-
11755 Default URL size is too small for cache key.
-
error
-
Cause: Default URL size was too small for cache key.
-
Action: No action required.
-
11757 Unsupported OTHER element specified in invalidation message: name='%s', type='%s', value='%s'.
-
warning
-
Cause: Unsupported OTHER element was specified in the invalidation message.
-
Action: See chapter "Sending Invalidation Requests" in the OracleAS Web Cache Administrator's Guide for all supported OTHER elements.
-
11800 CGI communication error.
-
Cause: Network I/O error while communicating with CGI application.
-
Action: No action required.
-
11802 Cannot open Service Manager: %s
-
alert
-
Cause: The admin server was unable open the Windows Service Manager.
-
Action: If the problem persists, contact Oracle Support.
-
11803 Cannot open Windows Service %s: %s
-
alert
-
Cause: The admin server was unable to open the specified service.
-
Action: If the problem persists, contact Oracle Support.
-
11804 Cannot obtain the system status for Windows service %s: %s
-
alert
-
Cause: The admin server was unable to retrieve the status for the specified service.
-
Action: If the problem persists, contact Oracle Support.
-
11805 Cannot control service %s: %s
-
alert
-
Cause: The admin server was unable to start or stop the specified Windows service.
-
Action: If the problem persists, contact Oracle Support.
-
11806 Cannot stop service %s
-
alert
-
Cause: The admin server failed to stop the specified service.
-
Action: If the problem persists, contact Oracle Support.
-
11807 Windows service, %s, stopped
-
notification
-
Cause: The admin server has successfully stopped the specified service.
-
Action: No action required.
-
11809 The admin server could not start the cache server, running in admin-only mode: %s
-
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.
-
11810 Cannot start Auto-Restart. %s does not exist
-
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.
-
11811 Unable to fork a new process for starting Auto-Restart.
-
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.
-
11812 Auto-Restart did not start. An error code was returned.
-
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.
-
11813 Cannot start service %s
-
alert
-
Cause: The admin server failed to start the specified service.
-
Action: If the problem persists, contact Oracle Support.
-
11814 Logging info: %s
-
error
-
Cause: An error is logged.
-
Action: Refer to the logged error details and take the appropriate action.
-
11815 The admin server process is unable to determine the OPMN auto-restart setting. Error reading or parsing %s
-
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.
-
11816 Error while changing the OPMN auto-restart setting for OracleAS Web Cache. Command: %s. Return code: %d. Command output: %s
-
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.
-
11817 Unable to allocate or access a shared memory segment of size %u bytes. %s(): %s
-
alert
-
Cause: The specified operating-system level function, which creates or accesses a shared memory segment of the size specified in the error message, has failed for the specified reason.
-
Action: This error usually occurs as a result of insufficient system resources. Refer to the included operating system level error message for further information.
-
11818 Login attempt fails to admin server process.
-
warning
-
Cause: An incorrect username or password was entered while attempting to access the admin server process. If this error occurs frequently, a malicious user might be attempting to crack the password
-
Action: Try the username and password again.
-
11901 SSL context creation failed, NZE-%d
-
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.
-
11902 SSL configuration fails, NZE-%d
-
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.
-
11903 SSL set credential fails, NZE-%d
-
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.
-
11904 SSL handshake fails NZE-%d
-
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.
-
11907 The server cannot allocate memory while in %s.
-
alert
-
Cause: The system has run out of memory.
-
Action: Restart the system and OracleAS Web Cache.
-
11908 SSL set peerid fails, NZE-%d
-
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.
-
11909 OracleAS Web Cache fails to get the name of communicating peer during SSL handshake, system error %d.
-
warning
-
Cause: OracleAS Web Cache could not determine peer IP Address.
-
Action: Contact Oracle Support.
-
11910 failed to normalize Wallet Resource Locator (WRL) %s
-
warning
-
Cause: WRL could not be parsed.
-
Action: Confirm that the WRL is in the correct format.
-
11913 SSL set hardware acceleration fails, NZE-%d.
-
alert
-
Cause: The 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.
-
11914 SSL set thread usage fails, NZE-%d.
-
warning
-
Cause: The 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.
-
11915 The SSL engine fails to initialize, NZE-%d.
-
warning
-
Cause: The 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.
-
11916 Oracle cryptographic toolkit context initialization fails, NZE-%d.
-
warning
-
Cause: The 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.
-
11917 SSL wallet %s file %s does not exist.
-
warning
-
Cause: The wallet was not found in the wallet directory.
-
Action: Check for wallet file ewallet.p12 or ewallet.der in the wallet directory.
-
11918 The SSL Wallet %s file %s is not readable.
-
warning
-
Cause: The wallet was not readable by OracleAS Web Cache.
-
Action: Check the file system permissions on this file.
-
11919 The SSL wallet autologin file %s does not exist. Wallet does not appear to be autologin wallet.
-
warning
-
Cause: The wallet autologin file cwallet.sso was not found.
-
Action: Check for wallet file cwallet.sso in wallet directory.
-
11920 The SSL wallet autologin file %s is not readable. Wallet does not appear to be autologin wallet.
-
warning
-
Cause: The wallet autologin file cwallet.sso was not readable by OracleAS Web Cache.
-
Action: Check the file system permissions on this file.
-
11921 The origin server wallet did not open. Operating without wallet for backend. Only Diffie-Hellman anonymous connections supported to origin servers.
-
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.
-
11922 %s wallet fails to open at location %s, NZE-%d, as user %s
-
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.
-
11923 %s wallet fails to open at location %s, NZE-%d.
-
warning
-
Cause: The wallet could not be opened
-
Action: Check for the existence of the wallet.
-
11924 Oracle wallet fails to open persona, NZE-%d.
-
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.
-
11925 No wallet configured with SSL; server initialization fails.
-
alert
-
Cause: SSL was configured without specifying a wallet.
-
Action: Correct the configuration file.
-
11926 OracleAS Web Cache fails to set cipher suite in SSL handshake, NZE-%d.
-
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.
-
11927 OracleAS Web Cache fails to get supported cipher suites, NZE-%d.
-
alert
-
Cause: The SSL library failed to get the supported cipher suites.
-
Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
-
11928 OracleAS Web Cache fails to set session reference, NZE-%d.
-
alert
-
Cause: The SSL library failed to get the supported cipher suites.
-
Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.
-
11929 SSL handshake fails NZE-%s.
-
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.
-
11950 Internal XML parser error. Error code: %d. Error Message: %s
-
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.
-
11951 invalid value for ESI redirect attribute
-
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.
-
11952 Start processing ESI document %s%s, nesting level %d
-
trace
-
Cause: Start processing of an ESI document (template or fragment).
-
Action: No action required.
-
11953 In ESI template %s%s, the fragment's site name and URL has been discovered as %s and %s
-
trace
-
Cause: Start processing of an ESI fragment.
-
Action: No action required.
-
11960 OracleAS Web Cache is unable to decode the URI passed in: %s
-
warning
-
Cause: URI decoding was unsuccessful, and it will be used as it is.
-
Action: No action required.
-
11962 OracleAS Web Cache is unable to allocate enough memory to parse ESI vars tag string.
-
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 and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager.
-
11963 OracleAS Web Cache failed to create new ESI fragment request. Template uri: %s
-
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 and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager.
-
11964 empty variable key in ESI vars tag
-
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.
-
11965 invalid variable name in ESI vars tag
-
error
-
Cause: The variable name specified in the ESI template by the ESI vars tag is not defined.
-
Action: See appendix "Edge Side Includes (ESI) Language Tags" in the OracleAS Web Cache Administrator's Guide for valid ESI variable names.
-
11966 In %s%s, request header failed to be added to the include request.
-
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 and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager.
-
11973 Site name cannot be resolved.
-
error
-
Cause: Requested site in ESI fragment request could not be resolved.
-
Action: Make sure that site name in the ESI request is correct.
-
11974 Incomplete URI for ESI fragment.
-
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.
-
11975 Corrupted data in ESI environment metadata block.
-
error
-
Cause: The application delivered data that could not be parsed to OracleAS Web Cache.
-
Action: Fix the application.
-
11976 Duplicate name %s in ESI environment metadata block.
-
trace
-
Cause: The environment block contained multiple name entries.
-
Action: Remove the duplicate entries. Only the first entry is used.
-
11977 Memory allocation failure while initializing login metadata hash table.
-
alert
-
Cause: The OracleAS Web Cache memory manager could not allocate any more memory.
-
Action: Adjust the maximum cache size in the Resource Limits and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager.
-
11978 In ESI template %s%s, failed to add request header value.
-
error
-
Cause: Wrong request-header was specified.
-
Action: Check the ESI template file and correct the error in request_header attribute.
-
11979 In ESI template %s%s, failed to add the request header because value is missing
-
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
-
11984 OracleAS Web Cache is unable to find the directory mapping to the default ESI fragment page %s.
-
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 Sites page or Oracle Enterprise Manager or the Error Pages of OracleAS Web Cache Manager.
-
11985 OracleAS Web Cache is unable to obtain the size of the default ESI fragment page %s.
-
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.
-
11986 The default ESI fragment page %s is too large.
-
alert
-
Cause: The default ESI fragment was too large.
-
Action: Alter the size of the default ESI fragment to less than 32 KB.
-
11987 OracleAS Web Cache fails to open the default ESI fragment page %s.
-
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.
-
11989 read error while loading default ESI fragment page %s
-
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.
-
11997 ESI stack overflow
-
error
-
Cause: Current stack maximum depth was set too low.
-
Action: Contact Oracle Support about how to increase the maximum stack depth.
-
12001 ESI <esi:include> tag nesting in template %s%s is too deep.
-
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 to change the maximum <esi:include> depth.
-
12002 Origin server busy exception in ESI template %s%s, fragment %s%s
-
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 Servers page of Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
12003 No connection exception in ESI template %s%s, fragment %s%s
-
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 Servers page of Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
12004 Network timeout exception in ESI template %s%s, fragment %s%s
-
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 Servers page of Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
12005 HTTP Client Error 4xx exception in ESI template %s%s, fragment %s%s
-
warning
-
Cause: The origin server returned an HTTP 4xx status code.
-
Action: Check for errors in the ESI template and fragment files.
-
12006 HTTP Server Error 5xx exception in ESI template %s%s, fragment %s%s
-
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.
-
12007 Incompatible fragment version exception in ESI template %s%s, fragment %s%s
-
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.
-
12008 Incorrect response header exception in ESI template %s%s, fragment %s%s
-
warning
-
Cause: The response header of the ESI fragment caused an error.
-
Action: Correct the error in the ESI fragment.
-
12009 Incorrect ESI fragment exception in ESI template %s%s, fragment %s%s
-
warning
-
Cause: OracleAS Web Cache was unable to parse the ESI fragment.
-
Action: Correct the error in the ESI fragment.
-
12010 Incorrect XML Fragment exception in ESI template %s%s, fragment %s%s
-
warning
-
Cause: OracleAS Web Cache was unable to parse the XML fragment.
-
Action: Correct the error in the XML fragment.
-
12011 Generic exception in ESI template %s%s, fragment %s%s
-
warning
-
Cause: A generic ESI exception occurred.
-
Action: Check the template and fragment, and then correct the error.
-
12012 No exception handler is defined in template %s%s:.
-
error
-
Cause: An uncaught ESI exception was detected. An error page is returned.
-
Action: Correct the syntax error in the ESI template.
-
12013 No resolved virtual host mapping was found for template.
-
trace
-
Cause: A ESI template contained an unresolved virtual host mapping.
-
Action: No action required.
-
12015 Non-fetchable inline fragment %s%s not found in cache or already expired, fetching template %s%s from origin server again.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12081 ESI parsing error. Dumping ESI content:
-
error
-
Cause: ESI parsing error.
-
Action: For any syntax errors, correct the ESI syntax. For any non-syntax related error, contact Oracle Support Services.
-
12082 OracleAS Web Cache cannot parse ESI due to insufficient memory.
-
error
-
Cause: OracleAS Web Cache ran out of memory while parsing ESI.
-
Action: Adjust the maximum cache size in the Resource Limits and Timeouts page of Oracle Enterprise Manager or Resource Limits page of OracleAS Web Cache Manager.
-
12083 ESI parser syntax error at line %d: %s
-
error
-
Cause: An ESI tag closed too early or there was a syntax error of the ESI parser.
-
Action: Correct the ESI syntax.
-
12085 ESI syntax error. Bad exception type at line %d.
-
error
-
Cause: An invalid token was encountered.
-
Action: Correct the error at the specified location in the ESI template.
-
12086 ESI syntax error. Unrecognized keyword %s is at line %d.
-
error
-
Cause: An invalid token was encountered.
-
Action: Correct the error at the specified location in the ESI template.
-
12087 Bad Location response header in ESI fragment response
-
error
-
Cause: A redirection response contained an invalid Location header.
-
Action: Make sure that the application Web server sends a valid Location header.
-
12088 ESI syntax error. The src attribute is missing at line %d.
-
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.
-
12089 Syntax error. The name attribute is missing at line %d.
-
error
-
Cause: 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.
-
12090 ESI syntax error. Bad attribute value appears at line %d.
-
error
-
Cause: An invalid or empty value string was found.
-
Action: Correct the error at the specified location in the ESI template.
-
12091 ESI syntax error. Multiple ESI <esi:environment> tags appear in a single template at line %d
-
error
-
Cause: Multiple <esi:environment> tags in a single ESI template are not allowed.
-
Action: Configure the ESI template with one <esi:environment> tag.
-
12092 ESI Syntax error. Multiple request_body elements appear at line %d.
-
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.
-
12093 ESI syntax error. The max-age attribute is incorrectly formatted at line %d.
-
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.
-
12094 ESI syntax error. String length exceeds maximum at line %d.
-
error
-
Cause: The string length exceeded the maximum limit.
-
Action: Contact Oracle Support to change the string length limit.
-
12095 ESI syntax error. A variable requires a key at line %d.
-
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.
-
12096 ESI syntax error. The POST request method requires an request_body at line %d.
-
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.
-
12097 ESI syntax error. The position of the <esi:environment> tag at line %d is invalid.
-
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.
-
12098 ESI syntax error. The value of the fetchable attribute at line %d is invalid.
-
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.
-
12099 ESI syntax error. The same attribute appears multiple times in an ESI element at line %d.
-
error
-
Cause: An attribute can appear only once within an ESI element.
-
Action: Correct the error at the specified location in ESI object.
-
12100 Exhausted process memory. Exiting process.
-
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.
-
12101 Maximum receive buffer size 2 MB reached.
-
error
-
Cause: Receive buffer size is bigger than 2 MB on Windows platforms.
-
Action: Reduce receive buffer size to below 2 MB.
-
12102 Unable to locate memory block (%db). OracleAS Web Cache extends cache size over maximum limit to %dMB.
-
alert
-
Cause: Memory request was not fulfilled with existing process memory, even after forced garbage collection.
-
Action: If the problem persists, contact Oracle Support.
-
12103 Unable to locate large memory block (%db). OracleAS Web Cache extends cache size over maximum limit to %dMB.
-
alert
-
Cause: Large block memory request was not satisfied with existing process memory, even after forced garbage collection.
-
Action: If the problem persists, contact Oracle Support.
-
12201 Cache memory allocation for the cluster member table failed.
-
error
-
Cause: Memory allocation failed.
-
Action: No action required.
-
12202 Cluster member DNS lookup problem
-
trace
-
Cause: Could not resolve the IP address from the cluster member's host name.
-
Action: Check the Cluster Members and Properties page of Oracle Enterprise Manager or the Clustering page of OracleAS Web Cache Manager to see if the host name is correctly listed.
-
12203 Cluster member number %s owner slot allocation %s:%s
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12204 Add cluster member number %s
-
notification
-
Cause: Normal notification behavior.
-
Action: No action required.
-
12205 Remove cluster member number %s
-
notification
-
Cause: Normal notification behavior.
-
Action: No action required.
-
12206 Cluster member number %s already marked alive
-
warning
-
Cause: The local cache tried to add the specified cluster member, but it was already marked as alive.
-
Action: No action required.
-
12207 Cluster member number %s already marked dead
-
warning
-
Cause: The local cache tried to remove the specified cluster member, but it was already marked as dead.
-
Action: No action required.
-
12209 A %s node cluster successfully initialized
-
notification
-
Cause: Normal notification behavior.
-
Action: No action required.
-
12212 Cluster member %s - %s configuration is invalid.
-
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.
-
12213 Cluster member %s - %s configuration is valid.
-
notification
-
Cause: Normal notification behavior.
-
Action: No action required.
-
12217 Cluster member count %s is larger than maximum allowed %s
-
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 Cluster Members and Properties page of Oracle Enterprise Manager or the Clustering page of OracleAS Web Cache Manager.
-
12400 HTTP request-header exceeds configured maximum individual header size ( %s ). Client IP: %s
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
12401 HTTP request-header exceeds configured maximum combined header size. Client IP: %s
-
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 Oracle Enterprise Manager OracleAS Web Cache Manager.
-
12402 HTTP response-header parsing error: %s.
-
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.
-
12403 HTTP response-header parsing error: %s ( %s ).
-
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.
-
12404 The number of search keys exceeds the maximum limit of search keys in the Surrogate-Key response-header.
-
warning
-
Cause: The number of search keys in the Surrogate-Key response-header exceeded the allowed configurable maximum defined in configuration file.
-
Action: Revise the Surrogate-Key response-header with configured maximum or fewer search keys.
-
12405 Illegal time format in HTTP response-header.
-
warning
-
Cause: HTTP response-header contains an illegal time format.
-
Action: No action required.
-
12409 Timeout while reading HTTP response.
-
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.
-
12410 Error while reading HTTP response ( SSL error %d ).
-
error
-
Cause: OracleAS Web Cache encountered an SSL read error.
-
Action: If the problem persists, contact Oracle Support.
-
12411 Non-parsable HTTP request-header line - questionable token syntax. Client IP: %s
-
warning
-
Cause: An HTTP request from a browser contained a line with a token value containing either an unpaired parenthesis ( ( or ) ) or an unpaired double-quote ("). For example: Cookie: name="John Hancock
-
Action: No action required.
-
12412 HTTP request-header parsing error - malformed request line. Client IP: %s
-
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.
-
12413 Unable to get Oracle name of ESI template character set ( %s ).
-
notification
-
Cause: A recoverable internal error occurred while doing character set conversion.
-
Action: No action required.
-
12414 Unable to get Oracle name of ESI fragment character set ( %s ).
-
notification
-
Cause: A recoverable internal error occurred while doing character set conversion.
-
Action: No action required.
-
12415 Unable to do character set conversion.
-
warning
-
Cause: A system/library call has unexpectedly failed.
-
Action: If the problem persists, contact Oracle Support.
-
12416 NLS library failure while doing character set conversion.
-
warning
-
Cause: A system/library call has unexpectedly failed.
-
Action: If the problem persists, contact Oracle Support.
-
12417 HTTP request-header parsing error - no header name. Client IP: %s
-
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.
-
12419 Dump of offending HTTP request-header line:
-
warning
-
Cause: Any of the causes associated with errors 12411, 12412 and 12417.
-
Action: No action required.
-
12420 The number of search keys exceeds the maximum hard limit of search keys in the Surrogate-Key response-header thus excessive search keys are discarded.
-
error
-
Cause: The number of search keys in the Surrogate-Key response-header exceeded the allowed hard maximum of 200.
-
Action: Revise the Surrogate-Key response-header with 200 or fewer search keys.
-
12421 HTTP request is invalid due to a duplicate header occurrence: "%s". Client IP: %s
-
error
-
Cause: An HTTP request from a browser contained multiple occurrences of the same header type.
-
Action: No action required.
-
12422 Duplicate header occurrence ("%s") is in HTTP request.
-
trace
-
Cause: An HTTP request from a browser contained multiple occurrences of the same header type.
-
Action: No action required.
-
12700 Site %s did not match any defined sites, resulting in no End User Performance Monitoring for URI
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12701 Site %s matched one of the defined sites for which End User Performance Monitoring is ON.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12702 Site %s matched a defined site with End User Performance Monitoring OFF, resulting in no End User Performance Monitoring for URI
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12703 No matching End User Performance Monitoring rule found for site %s, resulting in End User Performance Monitoring for URI.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required
-
12704 There are no End User Performance Monitoring rules defined for site %s, resulting in End User Performance Monitoring for URI.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12705 Matching End User Performance Monitoring REGEXP rule found regexp:%s and the rule is %s
-
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.
-
12706 Matching End User Performance Monitoring SUBSTRING rule found. substring:%s and the rule is %s
-
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.
-
12712 The end-user performance monitoring file can only be set to an .html file.
-
error
-
Cause: The file specified was not an .html file.
-
Action: Contact Oracle Support for help in specifying the correct end-user performance monitoring file.
-
12713 The end-user performance monitoring file cannot be parsed. Use the following format: <SCRIPT SRC="%schronos_JavaScript_filename"></SCRIPT> and restart OracleAS Web Cache.
-
error
-
Cause: The file could not be parsed.
-
Action: Use the following format for the value of the end-user performance monitoring file: <SCRIPT SRC="%schronos_JavaScript_filename"></SCRIPT>. Then, restart OracleAS Web Cache.
-
12714 Invalid string specified for the end-user performance monitoring file.
-
error
-
Cause: The file name specified was an invalid string.
-
Action: Contact Oracle Support for help in specifying the correct file.
-
12715 The end-user performance monitoring file contains an invalid path separator.
-
error
-
Cause: The file name specified contained an invalid path separator.
-
Action: Correct the file name specified.
-
12716 End-user performance monitoring is enabled.
-
notification
-
Cause: Normal notification behavior. End-user performance monitoring is enabled. The event is written to the log file.
-
Action: No action required.
-
12800 OracleAS Web Cache failed to read the configuration file. Dynamic changes have not been applied.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12801 Dynamic Changes Applied Successfully
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12802 The cache server cannot dynamically mark the origin servers as running because they are not responding. Other selected dynamic changes are applied.
-
trace
-
Cause: The origin servers were not responding. The cache server disregarded this dynamic change, but applied other dynamic changes.
-
Action: No action required.
-
12803 Dynamic Changes Not Applied
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12804 Event Log rolled over.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12805 Access log %s rolls over.
-
notification
-
Cause: Access log rolled over as a result of an on-demand rollover request.
-
Action: No action required.
-
12806 Non-existent access log %s specified in rollover request.
-
notification
-
Cause: On-demand rollover request was submitted with an invalid access log name.
-
Action: No action required.
-
12807 Event log not rolled over because the rollover file already exists.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12808 Access Log %s not rolled over because the rollover file already exists.
-
notification
-
Cause: Access Log is rolled over as a result of on-demand rollover request.
-
Action: Submit another rollover request after more than one minute.
-
12809 Could not find the matching Origin Server entry in original configuration which the cache server is running with.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
12810 ESI fragment log for access log %s is not rolled over.
-
notification
-
Cause: Regular access log was rolled over due to an on-demand rollover request, but accompanying ESI fragment log was not rolled over for some reason.
-
Action: Submit another rollover request after one minute.
-
12811 Dynamic event log rollover fails because the event log file does not exist.
-
alert
-
Cause: Dynamic event log rollover failed because Oracle Web Cache failed to create the event log file at startup time.
-
Action: Review the event log file name specified in configuration.
-
12812 Dynamic event log rollover fails because the event log file could not be renamed.
-
alert
-
Cause: Dynamic event log rollover failed because Oracle Web Cache could not rename the file.
-
Action: Check the permissions of the event log file or if any other application is using the event log file.
-
12901 OracleAS Web Cache fails to send the message to the Oracle Web Conferencing client; redirect fails.
-
Error
-
Cause: OracleAS Web Cache could not send Oracle Web Conferencing protocol message to client.
-
Action: No action required.
-
12902 The mx list is empty in the Oracle Web Conferencing path %s.
-
Alert
-
Cause: The configured mx path set was incorrect.
-
Action: Configure the correct mx path.
-
12903 The Oracle Web Conferencing pass descriptor fails; Error: %s.
-
Error
-
Cause: OracleAS Web Cache was unable to pass descriptor to the mx server.
-
Action: Check the mx server configuration and log files.
-
12904 Oracle Web Conferencing redirect didn't occur for mx path = %s.
-
Error
-
Cause: OracleAS Web Cache was not able to pass descriptor to the mx server on any of the mx server ports.
-
Action: Check the mx server configuration and log files.
-
12905 Oracle Web Conferencing redirect is successful.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required
-
12906 The Windows socket could not be set to blocking; Error: %s.
-
Error
-
Cause: The error was caused the by the error printed in the message.
-
Action: Debug from the error printed in the message.
-
12907 The Oracle Web Conferencing URL is not valid.
-
Error
-
Cause: The URL received by webcache is invalid.
-
Action: Check the Oracle Web Conferencing configuration.
-
12908 The Oracle Web Conferencing pass descriptor is successful.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
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.
-
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 Sites page of Oracle Enterprise Manager or Site Definitions page of OracleAS Web Cache Manager, correct the mapping. Then, restart OracleAS Web Cache.
-
13002 Maximum allowed incoming connections are %u
-
notification
-
Cause: Normal notification behavior indicating the maximum number of concurrent connections which will be accepted.
-
Action: No action required.
-
13003 Configuration error. Stopping admin or cache server.
-
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.
-
13007 The specified listening IP address "%s" is not valid.
-
alert
-
Cause: The specified listening IP address was not valid 32-bit dotted decimal notation, resolvable host name, ANY, or asterisk (*).
-
Action: 1. Check if the specified listening address is configured as a valid 32-bit numeric address written as four numbers separated by dots. Oracle Enterprise Manager permits * and OracleAS Web Cache Manager permits ANY to support all IP addresses. 2. If you need to specify host name instead of an IP address, check if the host name can be resolved to an IP address on your system. 3. If you need to rely on DNS to resolve the host name, check if DNS is correctly working.
-
13050 Multiple access logs use the same file name: %s
-
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.
-
13074 A session caching rule refers to an invalid session name: %s
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
Action: Edit webcache.xml and set the session ID to a valid session definition.
-
13075 A session binding rule refers to an invalid session name: %s
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
Action: Edit webcache.xml and correct the session definition for the specified session ID.
-
13076 A caching rule refers to an invalid expiration rule: %s
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
Action: Edit webcache.xml and find the specified expiration rule and replace it with a valid expiration rule.
-
13077 A caching rule refers to an invalid multi-version cookie rule: %s
-
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 Oracle Enterprise Manager or 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.
-
13078 A caching rule refers to an invalid session rule: %s
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
Action: Edit webcache.xml and find the specified session rule. Replace the rule with a valid one.
-
13079 No matching CACHE element found in webcache.xml for current hostname (%s) and ORACLE_HOME (%s)
-
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.
-
13080 No NAME attribute is specified in ROLLOVER element under ACCESSLOGSTYLES
-
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 does not have NAME attribute. Add the NAME attribute to the ROLLOVER element.
-
13081 Any Set-Cookie is not configured with the a session binding mechanism other than Cookie-based.
-
alert
-
Cause: A session binding rule specifying a session of Any Set-Cookie was not configured with the Cookie-based session binding mechanism. Any Set-Cookie cannot use a mechanism of OC4J-based or Internal-Tracking.
-
Action: Change the session binding mechanism to Cookie-based.
-
13106 Log file rollover schedule refers to an invalid TIME value for the HOURLY frequency: %u
-
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.
-
13107 Log file rollover schedule refers to an invalid TIME value for the DAILY frequency: %u
-
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.
-
13108 Log file rollover schedule refers to an invalid TIME value for the WEEKLY frequency: %u
-
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.
-
13109 XML parsing error in %s. Error code %u: %s
-
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.
-
13110 XML parser initialization error. Error code: %u
-
alert
-
Cause: Unable to initialize the XML parser.
-
Action: If the problem persists, contact Oracle Support.
-
13111 XML parsing failed for file: %s. Error Code: %u
-
alert
-
Cause: An XML parsing error occurred when parsing the specified file.
-
Action: Review associated error messages for more information about the problem.
-
13112 XML parsing failed. Error Code: %u
-
error
-
Cause: Failed to parse an XML message.
-
Action: Review associated error messages for more information about the problem.
-
13113 Syntax error in %s. Exception: "%s" in attribute "%s" having value "%s" in element %s
-
error
-
Cause: An exception occurred while parsing the specified file.
-
Action: Edit the specified file to make it a valid XML object.
-
13119 Duplicate origin server hosts specified for host %s port %s.
-
error
-
Cause: There are duplicate entries in the HOST section of the webcache.xml file.
-
Action: Remove the duplicate entries from webcache.xml.
-
13120 CACHEWITH and CACHEWITHOUT cannot both have the value "NO" in a session caching policy for session %s.
-
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.
-
13121 The caching rule for %s contains more than one multi-version cookie policy based on the same cookie: %s.
-
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.
-
13122 The caching rule for %s contains more than one session-caching policy based on the same session: %s.
-
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.
-
13123 Site name %s:%s%s exceeds maximum individual header limit.
-
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 of Oracle Enterprise Manager or OracleAS Web Cache Manager, or change the site name in the Sites page or Oracle Enterprise Manager or Site Definitions page of OracleAS Web Cache Manager, so that the site name and port number string together is less than the specified limit.
-
13124 Alias name %s:%s%s exceeds maximum individual header limit %d.
-
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 of Oracle Enterprise Manager or OracleAS Web Cache Manager, or change the alias name in the Sites page of Oracle Enterprise Manager or Site Definitions page of OracleAS Web Cache Manager, so that the alias name and port number string together is less than the specified limit.
-
13125 internal.xml does not have CALYPSOINTERNALPARAMS element.
-
error
-
Cause: Unable to find CALYPSOINTERNALPARAMS element in internal.xml.
-
Action: Check whether internal.xml conforms to internal.dtd.
-
13126 No default site defined. From OracleAS Web Cache Manager, change one site from Site Definitions to be default site.
-
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.
-
13127 Oracle XML Schema processor failed to initialize%s.
-
error
-
Cause: Oracle XML Schema Processor failed to initialize.
-
Action: If the problem persists, contact Oracle Support.
-
13128 XML file%s did not pass validation against schema checking%s.
-
error
-
Cause: Error occurs in validating the XML file against its corresponding XML schema
-
Action: Fix the error accordingly in the XML file
-
13200 Access logging was skipped as the request had not been parsed properly.
-
error
-
Cause: Due to an error in request parsing, access logging could not be completed.
-
Action: None
-
13212 Access log file %s could not be opened.
-
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.
-
13213 Invalid access log field name: %s
-
alert
-
Cause: An invalid access log field is specified in the configuration file webcache.xml.
-
Action: Set valid access log field name.
-
13215 I/O Error when writing access Log buffer to file. error number: %d
-
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.
-
13251 The HTML file for end-user monitoring was not found.
-
alert
-
Cause: There was a configuration error.
-
Action: Disable end-user monitoring or restore the HTML file that is missing.
-
13252 On Demand Log File Rollover for file %s was not successful. File %s could not be created.
-
warning
-
Cause: The rollover file could not be created.
-
Action: Check the file permissions.
-
13301 A failure occurred with DNS lookups. No more DNS lookups will occur.
-
warning
-
Cause: The DNS server might be unavailable.
-
Action: Check the DNS configuration on the local machine.
-
13302 Failed to open directory: %s
-
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.
-
13305 Failed to assign port %s: %s
-
alert
-
Cause: The selected port is being used by another application.
-
Action: Change the port to an unused port.
-
13306 Failed to configure resources for port %s: %s
-
alert
-
Cause: System listen function call failed.
-
Action: Restart OracleAS Web Cache.
-
13307 Failed to allocate resources for port, %s: %s
-
trace
-
Cause: Socket creation failed.
-
Action: If the problem persists, Restart OracleAS Web Cache and check open file descriptors.
-
13310 Problem opening file %s (Access Denied).
-
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.
-
13312 Problem opening file %s (File Already Exists).
-
warning
-
Cause: The file could not be created because it already exists.
-
Action: Choose a file name that does not exist.
-
13313 Problem opening file %s (Invalid Drive).
-
warning
-
Cause: The file could not be opened because the drive name is invalid.
-
Action: Correct the file specification.
-
13314 Problem opening file %s (Invalid Name).
-
warning
-
Cause: The file could not be opened because the file name is invalid.
-
Action: Correct the file specification.
-
13315 Problem opening file %s (Too Many Open Files).
-
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.
-
13316 Problem opening file %s (File Not Found).
-
warning
-
Cause: The file could not be opened because the file could not be found.
-
Action: Correct the file specification.
-
13317 Problem opening file %s (Sharing violation).
-
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.
-
13318 Problem opening file %s (Is a directory).
-
warning
-
Cause: The file could not be opened because it is directory.
-
Action: Correct the file specification.
-
13350 Error during network receive, system error %s
-
trace
-
Cause: There was system error during the networking receive.
-
Action: No action required.
-
13351 Timeout during network receive, socket number %s
-
error
-
Cause: There was timeout during the networking receive.
-
Action: No action required.
-
13365 Error during network send, system error %s
-
trace
-
Cause: There was system error during the networking send.
-
Action: No action required.
-
13366 Timeout during network send, socket number %s
-
trace
-
Cause: There was timeout during the networking send.
-
Action: No action required.
-
13380 Error during SSL handshake, system error %s
-
error
-
Cause: There was system error during the SSL handshake.
-
Action: No action required.
-
13381 Timeout during SSL handshake, socket number %s
-
error
-
Cause: There was timeout during the SSL handshake.
-
Action: No action required.
-
13382 File %s cannot be opened.
-
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.
-
13383 Unable to initialize DNS lookups
-
warning
-
Cause: Cannot use DNS for TCP/IP host resolution.
-
Action: No required action.
-
13400 parsing error of <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> at offset %d
-
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 object.
-
13601 Signal SIGSEGV caught
-
alert
-
Cause: Signal SIGSEGV is caught. Diagnostic information is printed in trace dump file.
-
Action: Contact Oracle Support.
-
13602 Signal SIGBUS caught
-
alert
-
Cause: Signal SIGBUS is caught. Diagnostic information is printed in trace dump file.
-
Action: Contact Oracle Support.
-
13603 Signal SIGFPE caught
-
alert
-
Cause: Signal SIGFPE is caught. Diagnostic information is printed in trace dump file.
-
Action: Contact Oracle Support.
-
13604 Signal SIGSEGV caught
-
alert
-
Cause: Signal SIGSEGV is caught. Diagnostic information is printed in trace dump file.
-
Action: Contact Oracle Support.
-
13704 Compression error in: %s
-
error
-
Cause: A gzip library call failed.
-
Action: If the problem persists, contact Oracle Support.
-
13705 OracleAS Web Cache compresses object. Original size: %d bytes; Compressed size: %d bytes.
-
trace
-
Cause: Normal trace behavior.
-
Action: No action required.
-
13708 Compression is not yielding any benefit.
-
trace
-
Cause: Compression was not able to reduce the size of the object.
-
Action: Disable compression for this object..
-
14002 Error while sending the request to origin server
-
warning
-
Cause: The request to the origin server failed.
-
Action: Ensure that the origin server is running.
-
14003 Error while receiving response from the origin server
-
warning
-
Cause: OracleAS Web Cache was unable to receive a response from the origin server.
-
Action: Ensure that the origin server is running.
-
14004 HTTP status code error
-
warning
-
Cause: The origin server returned a non-HTTP status code.
-
Action: Check the origin server to determine what application is sending the response.
-
14005 Content-Type buffer is too small
-
warning
-
Cause: The buffer pool memory was not sufficient.
-
Action: Adjust the maximum individual header size limit in the Security page of Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
14006 SSL handshake with origin server fails.
-
warning
-
Cause: The SSL handshake between OracleAS Web Cache and the origin server failed.
-
Action: Check certificate configuration on the origin server.
-
14007 Connect request terminates.
-
warning
-
Cause: The connection request to the origin server was terminated.
-
Action: If the problem persists, contact Oracle Support.
-
14008 Create request fails.
-
warning
-
Cause: OracleAS Web Cache failed to create a request to the origin server.
-
Action: If the problem persists, contact Oracle Support.
-
14009 Header operation fails.
-
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.
-
14010 Invalid authentication credentials for proxy server
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
14011 Proxy tunnel authentication required
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
14012 Bad response from proxy tunnel
-
warning
-
Cause: The proxy tunnel response was incorrect.
-
Action: Check the proxy server configuration and setup.
-
14013 Send request to origin server times out.
-
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 Resource Limits and Timeouts page of Oracle Enterprise Manager or Network Timeouts page of OracleAS Web Cache Manager.
-
14014 Receive request from origin server times out.
-
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 Resource Limits page Oracle Enterprise Manager or Network Timeouts page of OracleAS Web Cache Manager.
-
14015 Browser terminates connection; the request to the origin server is terminated.
-
warning
-
Cause: The browser terminated its connection. As a result, OracleAS Web Cache terminated its connection to the origin server.
-
Action: No action required.
-
14016 Connection to origin server fails.
-
warning
-
Cause: The origin server is down.
-
Action: Check the origin server.
-
14017 Connection to origin server times out.
-
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 Resource Limits and Timeouts of Oracle Enterprise Manager or Network Timeouts page of OracleAS Web Cache Manager.
-
14018 Socket creation fails for origin server.
-
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 and Timeouts page of Oracle Enterprise Manager or Resource Limits of OracleAS Web Cache Manager.
-
14019 Dynamic origin server DNS failure
-
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 Sites page of Oracle Enterprise Manager or Site-to-Server Mapping page of OracleAS Web Cache Manager.
-
14020 Origin server rejects queue entry.
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
14021 Capacity, as set by Web Cache, is exceeded for all origin servers that are available for processing this request.
-
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 Oracle Enterprise Manager or OracleAS Web Cache Manager.
-
14022 Load balancing and failover functionality fails.
-
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.
-
14023 No origin server is running.
-
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.
-
14024 Dynamic origin server is not allowed for request.
-
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 Sites page of Oracle Enterprise Manager or Site Definitions and Site-to-Server Mapping page of OracleAS Web Cache Manager.
-
14025 Dynamic connection to origin server fails.
-
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.
-
14027 Connection request times out.
-
warning
-
Cause: The connection between OracleAS Web Cache and the origin server timed out.
-
Action: No action required.
-
14028 incomplete header
-
warning
-
Cause: The HTTP response from the origin server did not contain a properly formatted HTTP header.
-
Action: Check the application sending the response.
-
14029 invalid header
-
warning
-
Cause: The HTTP header response from the origin server contained an invalid field.
-
Action: Check the application sending the response.
-
14032 Buffer finished before is found.
-
warning
-
Cause: The response from the origin server was not properly formatted.
-
Action: If the problem persists, check the application sending the response.
-
14036 time overflow
-
warning
-
Cause: Invalid time string from Origin Server
-
Action: Check the Origin Server configuration setting
-
14037 illegal time format
-
warning
-
Cause: The creation time received from the origin server was for a time in the future.
-
Action: Check the application sending the response.
-
14039 HTTP response not found
-
warning
-
Cause: An HTTP response from the origin server was not found.
-
Action: Check the application sending the response.
-
14041 invalid format
-
warning
-
Cause: The response contained an invalid time format or inversion of an integer.
-
Action: No action required.
-
14044 Unexpected EOF while reading HTTP response-header.
-
error
-
Cause: Connection prematurely closed by origin server.
-
Action: No action required.
-
14045 Error Parsing Chunk Length for %s%s.
-
error
-
Cause: Incorrect chunk length
-
Action: No action required.
-
14047 OracleAS Web Cache encounters an invalid HTTP response.
-
error
-
Cause: An HTTP response from the origin server contained invalid contents. For example, the response indicated chunked contents but the response contained no chunks.
-
Action: Check the application sending the response.
-
20101 Open socket fd=%d exceeded FDArr_Size %d.
-
alert
-
Cause: Potential file descriptor leakage.
-
Action: Contact Oracle Support.
-
20150 Failure in scheduling asynchronous task: %s.
-
alert
-
Cause: Potential memory shortage. Note: This is for all asynchronous functions.
-
Action: Contact Oracle Support.