Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1.6.0)

Part Number E10113-09
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

105 WXE-00010 to WXE-21271

WXE-00010: %s
Cause: Internal error raised.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-00800: Auto-Restart started successfully
Cause: The Auto-Restart process has successfully completed its initialization.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-08000: Internal error. Auto-Restart process terminating.
Cause: An internal error occurred in the Auto-Restart process.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. This error usually occurs as a result of insufficient system resources. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Process

WXE-08001: Failed to start the cache server. Auto-Restart process terminating.
Cause: Failed to start the Oracle Web Cache server.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. This error usually occurs as a result of insufficient system resources. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Process

WXE-08002: Failed to find an Oracle Web Cache listening port that does not require SSL client-side certificates. Auto-Restart pinging is disabled.
Cause: Auto-Restart does not support the use of client-side certificates. If all Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-08500: Cache server not responding on port %d.
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: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-08501: Timeout occurred communicating with the cache server.
Cause: The cache server was either in an unstable state or slow responding to queries.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. From the Auto-Restart page of Oracle Enterprise Manager or Oracle Web Cache Manager, check the ping timeout interval and increase it if necessary.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-08502: Lost connection with the cache server.
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: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-08503: Operating system level error in %s() (%d): %s.
Cause: The specified system call returned the specified error.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Operating System

WXE-08504: %u consecutive errors pinging the cache server.
Cause: The Auto-Restart process received the specified number of failures when attempting to reach the cache server.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-08505: %u consecutive error(s) pinging the cache server. %d error(s) required for restart.
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: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-08506: Unable to retrieve the cache server process ID from %s. Stopping the Auto-Restart process.
Cause: Unable to read the Oracle 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: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-08507: Cache server process not running.
Cause: There was no process on the system matching the process ID listed in the Oracle Web Cache server pid file.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Process

WXE-08508: Restarting the cache server.
Cause: See accompanying error messages for more information.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: ERROR

Impact: Process

WXE-08509: Starting the cache server.
Cause: See accompanying error messages for more information.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: ERROR

Impact: Process

WXE-08510: SSL set hardware acceleration failed. NZE-%d.
Cause: The SSL library failed to initialize the hardware SSL acceleration. The specified error message provides more detail.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

Level: 16

Type: ERROR

Impact: Security

WXE-08511: SSL Set Thread Usage Failed. NZE-%d.
Cause: The SSL library failed to set the threading model. The specified error message provides more detail.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

Level: 16

Type: ERROR

Impact: Security

WXE-08512: SSL Engine Failed to Initialize. NZE-%d.
Cause: The SSL engine failed to initialize. The specified error message provides more detail.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

Level: 16

Type: ERROR

Impact: Security

WXE-08513: Cache server process ID %u is starting up.
Cause: The cache server is starting up.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Process

WXE-08514: Cache server process ID %u is shutting down.
Cause: The cache server is shutting down.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Process

WXE-08515: Event log message %d (%s) referenced %d time(s)
Cause: Occurrence frequency of various event_log message
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-08516: Event log index %d contains %d node(s)
Cause: Occurrence frequency of various event_log message
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-09000: Oracle Web Cache process of ID %d exits with code %d at line %d of file %s [label: %s]
Cause: The Oracle Web Cache process shutdown.
Action: No action required.

Level: 1

Type: ERROR

Impact: Process

WXE-09001: An error occurred while disabling core file creation.
Cause: Internal error. The system/library call to disable core file creation returned an error.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Logging

WXE-09003: File %.*s open failed; using %.*s instead
Cause: The attempt to open the specified file failed. Oracle Web Cache opened the new file instead.
Action: No action required.

Level: 1

Type: WARNING

Impact: Logging

WXE-09200: An error occurred while trying to create a background process.
Cause: Could not open standard input while Oracle Web Cache is creating a process.
Action: Determine why Oracle Web Cache cannot read standard input or write to standard output for null device.

Level: 1

Type: ERROR

Impact: Process

WXE-09401: %s[%d].%s: %s
Cause: Statistics information dumped to event log on server shutdown
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09402: %s[%d].%s: %ld
Cause: Statistics information dumped to event log on server shutdown
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09403: Maximum number of file/socket descriptors set to %s.
Cause: The specified number of file descriptors is set for use by Oracle Web Cache.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09404: DMS metadata load starting
Cause: Loading DMS metadata information
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09405: DMS metadata load complete
Cause: Loading DMS metadata information
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09411: DMS shutdown starting
Cause: Loading DMS metadata information
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09412: DMS shutdown complete
Cause: Loading DMS metadata information
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09418: DMS disabled
Cause: Loading DMS metadata information
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09420: Error accessing the Oracle Dynamic Monitoring Service library, %s: %s
Cause: An error occurred when attempting to open or access functions in the Oracle Dynamic Monitoring Service (DMS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found" or function not available".
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09421: Unable to open the Oracle Dynamic Monitoring Service library, %s:%s. Searching the library path.
Cause: An error occurred when attempting to open the Oracle Dynamic Monitoring Service (DMS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found". Oracle Web Cache will search the library path. If the library is still not / found, then Oracle Web Cache returns event message 09420. NOTE: DMS statistics collection has been disabled until the problem is resolved.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-09422: Error accessing %s in the Oracle Dynamic Monitoring Service library, %s: %s
Cause: An error occurred when attempting to open or access functions in the Oracle Dynamic Monitoring Service (DMS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found" or function not available".
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09424: The statistics persistent repository is disabled
Cause: The statistics persistent repository has been disabled by the user in the webcache.xml configuration file.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09425: The %s file is no longer valid
Cause: The wcstatsrepos.xml file has been modified since the cache was started. The contents and/or changes are ignored.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09426: The %s statistics persistent repository does not exist
Cause: The wcstatsrepos.xml file statistics persistent repository does not exist; this may be the first time the repository has been accessed.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09427: Failure during file move of %s. Statistics persistent repository is abandoned
Cause: File move or rename failed.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09428: An error occurs during statistics repository download. The file %s has been corrupted or moved.
Cause: The "wcstatsrepos.xml" file was corrupted or moved during the shutdown operation.
Action: Recover "wcstatsrepos.xml" by copying from "wcstatsrepos.bak".

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09429: Failed to open the %s file. Statistics persistent repository is abandoned
Cause: Failed to open the "wcstatsrepos.tmp" temporary file.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09430: Failure creating the %s file. Statistics persistent repository is abandoned
Cause: Failed to write to or close the "wcstatsrepos.tmp" temporary file.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09431: The statistics persistent repository is being reset by new version
Cause: The statistics persistent repository has been invalidated by the installation of a new Oracle Web Cache software version
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09432: Starting statistics persistent repository checkpoint operation
Cause: The statistics persistent repository is being checkpointed.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09433: Completed statistics persistent repository checkpoint operation
Cause: The statistics persistent repository is being checkpointed.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09438: The statistics persistent repository is being reset by new configuration
Cause: The statistics persistent repository has been invalidated by a change to the Oracle Web Cache configuration file (webcache.xml)
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09440: The statistics persistent repository is disabled by event
Cause: The statistics persistent repository has been disabled because the "last" event is marked as "VALID=NO".
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09441: DMS enabled
Cause: Loading DMS metadata information
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09442: Unable to resolve APIs in the Oracle Dynamic Monitoring Service library, %s:%s
Cause: An error occurred when attempting to resolve public APIs in the Oracle Dynamic Monitoring Service (DMS) library.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09443: All APIs in the Oracle Dynamic Monitoring Service library have been resolved
Cause: All external APIs have been identified and properly resolved.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09444: The statistics persistent repository cannot be processed: %d
Cause: The statistics persistent repository has been determined to not match the current statistics configuration.
Action: No action required. The statistics repository will be rebuilt automatically at the next specified checkpoint interval or when the webcache server shuts down.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09445: Dynamic Metric Services allocating excessive memory block:%d
Cause: The Dynamic Metric Services (DMS) is allocating a memory buffer that is potentially too large.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-09446: Statistics initialization commencing.
Cause: The statistics information initialization operation is beginning.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-09447: Statistics initialization complete.
Cause: The statistics information initialization operation is complete.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-09521: Oracle Web Cache fails to find user ( %s ) in /etc/passwd.
Cause: The specified user was not found in the password file.
Action: Add user to the password file.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09522: Oracle Web Cache fails to find group ( %s ) in /etc/group.
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 Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09523: Invalid user ID ( %s ).
Cause: The specified user ID was invalid.
Action: Correct the user ID in the Security page of Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09524: Invalid group ID ( %s )
Cause: The specified group ID was invalid.
Action: Correct the group ID in the Security page of Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09525: Permission denied when setting user ID ( %s ).
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09526: Permission denied when setting group ID ( %s ).
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09534: Unexpected File I/O Error ( %s ) when opening file %s.
Cause: Could not open specified file.
Action: Review specified error to determine the problem on your system.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09570: Directory not found when unlinking file %s
Cause: The directory was not found.
Action: Verify that Oracle Web Cache was installed properly. You may need to reinstall Oracle Web Cache.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09571: Too many files open when unlinking file %s.
Cause: Too many files were open for available system resources.
Action: Adjust system resources and restart Oracle Web Cache.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09572: No disk space available when unlinking file %s
Cause: Insufficient disk space was available on the system.
Action: The system is running low on disk space. Free up disk space and restart Oracle Web Cache.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09573: Unexpected File I/O Error ( %s ) when unlinking file %s.
Cause: There was an unexpected input/output file error.
Action: Review the specified error and correct the problem on the system.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09574: Permission denied when unlinking file %s.
Cause: Permission denied on file.
Action: Set correct permission on the specified file.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09600: SIGTERM caught - program will shut down once all connections are complete.
Cause: Normal notification behavior. Shutdown event written to the log file.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09601: SIGUSR1 caught - program will reread configuration files after all connections are complete.
Cause: Normal notification behavior. Configuration file reread event written to the log file.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09602: All configuration files have been reread.
Cause: Normal notification behavior. All configuration files have been reread and this configuration reload event written to the log file.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WXE-09603: There was an error rereading the configuration files. The program is exiting.
Cause: Invalid Oracle Web Cache configuration files.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the Oracle Web Cache configuration files and restart Oracle Web Cache.

Level: 1

Type: ERROR

Impact: Configuration

WXE-09604: Could not increase the number of file/socket descriptors to %s.
Cause: Ran out of file descriptors on the system.
Action: Decrease the Maximum Incoming Connections value in the Resource Limits of Fusion Middleware Control, or increase the system file descriptors. Run Oracle Web Cache as the root user.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09605: Cannot create OPMN shutdown thread. Continuing with startup.
Cause: Oracle Web Cache could not create OPMN shutdown thread.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Use OPMN to abort the Oracle Web Cache process during Oracle Web Cache shutdown.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09606: Cannot create OPMN shutdown event. Continuing with startup.
Cause: Oracle Web Cache could not create OPMN shutdown event.
Action: Use OPMN to abort the Oracle Web Cache process during Oracle Web Cache shutdown.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09607: The admin server started successfully.
Cause: The Oracle Web Cache admin server process started successfully.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: NOTIFICATION

Impact: Process

WXE-09608: The cache server process started successfully.
Cause: The Oracle Web Cache server process has started successfully.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Process

WXE-09609: The server process could not initialize.
Cause: The Oracle Web Cache configuration is invalid.
Action: Review the error log file or use the Event Viewer to help determine the cause of the problem.

Level: 1

Type: ERROR

Impact: Process

WXE-09610: The server is exiting.
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.

Level: 1

Type: NOTIFICATION

Impact: Process

WXE-09611: The server could not start the service thread.
Cause: The server process could not start the Service thread.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Determine why Oracle Web Cache cannot start a thread on your system.

Level: 1

Type: ERROR

Impact: Threads

WXE-09612: Oracle Web Cache %s, %s
Cause: Normal notification behavior. The Oracle Web Cache version number was written to the log file.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09614: The following Oracle Web Cache internal files are pre-populated to the cache: [[ %s ]]
Cause: The specified Oracle Web Cache internal files are loaded into the cache.
Action: No required action.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09615: SMALLDOCBUFFERSIZE larger than DOCBUFFERSIZE. Setting SMALLDOCBUFFERSIZE=%s
Cause: Invalid Oracle Web Cache configuration. The SMALLDOCBUFFERSIZE is larger than DOCBUFFERSIZE.
Action: Review your configuration. Oracle Web Cache will override your current configuration for SMALLDOCBUFFERSIZE.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-09616: The Oracle Web Cache is running in the routing only mode.
Cause: The Oracle Web Cache is running in the routing only mode.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09700: Unable to initialize NLS. Error %d
Cause: Internal error. A system/library call has unexpectedly failed.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09701: Unable to initialize NLS global structure.
Cause: Internal error. A system/library call has unexpectedly failed.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09702: NLS boot file not found or missing; using default.
Cause: Internal error. A system/library call has unexpectedly failed.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-09703: Stop Issued. The program will shut down after all accepted requests are served, or a timeout occurs.
Cause: Stop was issued.
Action: Oracle Web Cache will be stopped.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09704: Abort Issued. The program will shut down immediately.
Cause: Abort was issued.
Action: Oracle Web Cache will be stopped immediately.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09705: Error accessing the Oracle Notification Service library, %s: %s
Cause: An error occurred when attempting to open or access functions in the Oracle Notification Service (ONS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found" or function not available".
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09706: Ignoring unrecognized option: %s
Cause: An alert was logged.
Action: Refer to the logged alert details and take the appropriate action.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09707: Failed to start the server.
Cause: Failed to start the Oracle Web Cache server. This error usually occurs as a result of insufficient system resources or invalid configuration.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Process

WXE-09708: Failed to initialize DNS
Cause: Failed to initialize DNS.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09709: Failed to initialize the HTTP component
Cause: Failed to initialize HTTP.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09710: Cache server failed to initialize.
Cause: Insufficient system resources or invalid Oracle Web Cache configuration.
Action: Review the error log file or use the Event Viewer to help determine the cause of the problem.

Level: 1

Type: ERROR

Impact: Process

WXE-09711: Problem loading message file for event log. Exiting.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09712: Unable to open the Oracle Notification Service library, %s:%s. Searching the library path.
Cause: An error occurred when attempting to open the Oracle Notification Service (ONS) library. See the operating system level error message included in this message. The error message provides further details, such as "file not found". Oracle Web Cache will search the library path. If the library is still not / found, then Oracle Web Cache returns event message 09705.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-09716: LDMInit Error %d
Cause: LDM library cannot be initialized
Action: Check the error number

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09717: LDMOpen Error %d
Cause: LDM repository cannot be opened
Action: Check the error number

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09718: eOns component already initialized; continuing...
Cause: The eOns component could not be initialized directly by the Oracle Web Cache server because eOns has already been previously initialized. The Oracle Web Cache server will continue to startup.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-09719: Initializing eOns component using port %s.
Cause: The eOns component is being initialized with the identified port number
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09720: req-info
Cause: Logging request information to the event_log.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09721: Cluster initialization failure.
Cause: Cluster initialization fails.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09722: Could not create specified access_log file.
Cause: The access_log was unable to be created.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09723: Could not establish effective user identification.
Cause: Could not establish the effective user identification. This may indicate an improper installation.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-09732: Oracle Instance configuration directory is not available.
Cause: One of the these environment variables, ORACLE_INSTANCE, COMPONENT_TYPE, or COMPONENT_NAME, is not defined.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Configuration

WXE-09733: The configuration file webcache.xml cannot be found.
Cause: The Oracle Web Cache instance may not be provisioned correctly or the file system is full.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Configuration

WXE-09807: Statistics query fatal error: %.*s
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-09811: Unknown value type:%d
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09812: Unknown instruction value type:%d
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09813: Bad operator in stack:%d
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09814: Unknown variable value type:%d
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09815: Unknown variable type:%d
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09816: Invalid register index
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09817: Invalid address value type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09818: Incompatible operands
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09819: Unknown value type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09820: Invalid addition operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09821: Invalid subtraction operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09822: Invalid less-than operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09823: Invalid less-than-equal operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09824: Invalid greater-than operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09825: Invalid greater-than-equal operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09826: Invalid multiply operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09827: Invalid division operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09828: Division by zero exception
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09829: Invalid modulo operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09830: Invalid shift-left operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09831: Invalid shift-right operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09832: Invalid bitwise-AND operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09833: Invalid exclusive-OR operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09834: Invalid inclusive-OR operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09835: Invalid function index type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09836: Invalid instruction:%d
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09837: Stack overflow
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09838: Bad expression
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09839: Assignment needs an lvalue
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09840: Missing an operand
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09841: Assignment needs an lvalue
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09842: Missing expression ')'
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09843: Missing function '('
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09844: Missing function ')'
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09845: Unexpected character in input: '%c'
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09846: Too many variables
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09847: Unterminated string
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09848: Unterminated string
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09849: Unknown column number (only %d columns available)
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09850: Builtin function %s() argument type mismatch
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09851: Invalid logical-OR operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09852: Expression already compiled
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09853: Expression not yet compiled
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09854: Invalid logical-AND operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09855: Unknown statistics group member %.*s
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09856: Invalid ones-complement operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09857: Invalid negation operand type
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09858: Invalid regular expression: %.*s
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09859: Expression context has not been initialized
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09860: Incorrect function argument separator usage
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09861: Invalid register name: '%c'
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09862: Expression too complex
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09863: Invalid row %d specified when %d rows exist; no value obtained
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-09864: Query operation not yet implemented or supported: %s
Cause: The statistics query failed for the specified reason.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-10054: Unable to resume service, UIPI return value is %s.
Cause: Service could not be resumed.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Review the error to determine the problem on your system.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-10417: MIME Type Extension ( %s ) exceeds current size limit.
Cause: Unexpected MIME type configured.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-10418: Encoding Extension ( %s ) exceeds current size limit.
Cause: Unexpected encoding type configured.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-10419: Language Extension ( %s ) exceeds current size limit.
Cause: Unexpected language type configured.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-10536: You must specify a full path for %s. See %s %s.
Cause: Failed to specify full path name.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Specify a full path name for the file.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-10555: Bad integer value ( %s ). See %s %s.
Cause: Invalid drive letter.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-10599: Unexpected error
Cause: Unexpected internal error.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11057: Dynamic origin server capacity is reduced to %d.
Cause: Oracle Web Cache ran out of file descriptors on the computer.
Action: Increase the file descriptor limit. See the Oracle Fusion Middleware Secure Proxy Caching and Load Balancing Guide for Oracle Web Cache.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11058: Stale object updated for %.*s%.*s
Cause: The complete response was successfully received and the cache entry is updated with the new response.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11059: Garbage object updated for %.*s%.*s
Cause: The complete response was successfully received and the cache entry is updated with the new response.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11060: Object update aborted.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11062: <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tag parsing error
Cause: The syntax for the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags was incorrect.
Action: Correct the syntax of the <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> tags in the source.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11064: ESI object %.*s%.*s parsing error
Cause: Object contained invalid ESI syntax.
Action: Correct the ESI syntax in the source.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11076: Cluster member %s - %s sent invalid configuration error
Cause: The cache cluster member sent a response to Oracle 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: This message is no longer used as of Oracle Fusion Middleware 11g. Compare the two configuration files, and then propagate the proper version to all cluster members.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11077: Cluster member sent invalid configuration error
Cause: The cache cluster member sent a response to Oracle 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: This message is no longer used as of Oracle Fusion Middleware 11g. Compare the two configuration files, and then propagate the proper version to all cluster members.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11078: Malformed environment object %.*s%.*s
Cause: The syntax of the XML file specified by the ESI environment is incorrect.
Action: Check the XML object for possible syntax errors.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11081: error while setting up the URI for +wcdebug for peer
Cause: Not applicable
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11082: error while constructing Inter-Cache Communication (ICC) header
Cause: Not applicable
Action: No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11083: Proxy server configuration error: %s
Cause: The proxy server was not correctly configured.
Action: Check the proxy server configuration in the Origin Servers page of Fusion Middleware Control and the general configuration of the proxy server itself.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11085: Authentication for the remote or subscriber cache is being challenged by a central or provider cache. Retry.
Cause: Access to the central or provider cache requires authorization.
Action: Try accessing the cache again.

Level: 1

Type: TRACE

Impact: Security

WXE-11086: Retry-capable request removed from server %d
Cause: The request was sent to an origin server that was unable to service the request due to the specified error code. Other servers exist that might be able to service this request, so the server is being marked as "serviced
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11088: Following URL is now in cache:
Cause: The complete response was successfully received and populated into the cache.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11089: Error while sending the entity body to the origin server
Cause: Oracle Web Cache encountered a bad network connection or the origin server was down.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11091: Error while processing ESI for %.*s%.*s
Cause: An error was encountered while ESI processing was done for the response. The page will not be cached.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11092: Object validated for %.*s%.*s
Cause: The cached object was validated by the origin server and its expiration timestamps were updated accordingly.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11093: Content-Length value %d sent by origin server does not match number of bytes received, that is %d bytes for %.*s%.*s.
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11095: Update fails because object is no longer cacheable.
Cause: This request was no longer cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11096: Retry-capable request failed with error %s
Cause: The request was sent to an origin server that was unable to service the request due to the specified error code. Other servers exist that might be able to service this request, so the request is being re-submitted to another server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11097: Retry-capable request submitted to another server (%d of %d)
Cause: The request was sent to an origin server that was unable to service the request due to the specified error code. Other servers exist that might be able to service this request, so the request is being re-submitted to another server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11101: Unable to acquire write lock while inserting objects, cache insertion fails.
Cause: Read/write lock acquire fails.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11104: Unknown state in voluntary garbage collection
Cause: Unknown state in voluntary garbage collection.
Action: No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11110: The maximum cache size is set too low. Oracle Web Cache failed to initialize.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11111: Based on maximum cache memory limit %s, a cache table is created.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11118: Duplicate search key %.*s found in Surrogate-Key response header is discarded.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11119: The number of search keys changed.
Cause: The number of search keys has changed for the same cached object.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11126: Unable to start voluntary garbage collection fiber.
Cause: numHashBuckets_x < MINIMUM_CACHE_HASHTABLE_SIZE
Action: No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11128: A duplicate cache insertion is found. Cache insertion fails.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11136: An error occurs during shutdown. The internal.xml file has been corrupted or moved.
Cause: The internal.xml file was corrupted or moved during the shutdown operation.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Recover internal.xml by copying from internal.xml.bak.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11138: Maximum number of versions is reached.
Cause: The number of versions in a cache entry has reached the maximum specified in the configuration.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11141: Traditional style basic key composed as %.*s.
Cause: Traditional style basic key composed.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11142: Traditional style cache key composed as %.*s.
Cause: Traditional style cache key composed.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11201: Oracle Web Cache is unable to resolve the IP address of %s. Check your DNS setup.
Cause: Oracle 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 Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11202: Origin server %s does not use IPv4.
Cause: Oracle 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: This message is no longer used as of Oracle Fusion Middleware 11g. 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 Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11203: Oracle Web Cache fails to connect to the origin server (id=%d).
Cause: An origin server is not available.
Action: Check the status of the origin server and the network connection.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11205: Oracle Web Cache marks the origin server %s (id=%d) as down and removes all session information bound to it.
Cause: The origin server was disabled or reached its failover threshold. Oracle 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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11206: Oracle Web Cache is unable to start pinging the origin server. rc code=%d
Cause: There was a potential memory allocation error.
Action: Check the configured memory usage in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11207: Origin server %s (id=%d) is down; Oracle Web Cache starts polling for status.
Cause: The origin server reached its failover threshold. Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11208: Cache cluster member %s (id=%d) is down; cache cluster members start polling for status. Ping threshold set at %d.
Cause: The cache cluster member reached its failover threshold. Oracle Web Cache reassigns ownership of cache content, and polls the failed cache cluster member for its status.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11209: Origin server %s (id=%d) is back up; Oracle Web Cache stops polling and restores origin server.
Cause: The ping URL to the origin server succeeded.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11210: Cache cluster member %s (id=%d) is up; cache cluster members stop polling and restore it.
Cause: The ping URL to the cache cluster member succeeded.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11211: All origin servers for site %s are down. Last origin server was (id=%d).
Cause: All origin servers configured for the site are down.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11212: Cache cluster member %s (id=%d) pinged successfully. %d successful pings so far.
Cause: An origin server is not available.
Action: Check the status of the origin server and the network connection.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11220: Session binding routing to origin server %s:%u (id=%d) for site %.*s
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11221: The origin server request is queued for site %.*s and site-to-server mapping %s.
Cause: The origin server was busy.
Action: Increase the capacity of the origin servers used by the site-to-server mapping.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11222: The origin server request is dropped due to a full queue for site %.*s and site-to-server mapping %s.
Cause: The origin server request queue was full.
Action: Increase the capacity of the origin servers used by the site-to-server mapping.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11223: The origin server request is routed to peer cache cluster member %s (id=%d) for site %.*s.
Cause: The request did not support session binding, and the requested object was owned by the peer cache cluster member.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11224: Site %.*s matches site-to-server mapping %s.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11225: Oracle Web Cache cannot find any running origin servers to route the request for site %.*s.
Cause: All origin servers are down.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11226: The session binding request is to a busy origin server %s:%u (id=%d) for site %.*s.
Cause: The session binding request was to a server was that was busy.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11227: Initial Request is routed to origin server %s using load balancing.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11228: No defined origin server can serve this request for site %.*s. The request is dropped.
Cause: This request was for a non-ESI page or for an ESI template and no matching site-to-server mapping was found. Dynamic origin servers are not allowed for these requests.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11229: This ESI fragment request is forwarded to a dynamic origin server for ESI provider site %.*s.
Cause: The request was for an ESI fragment without a matching site-to-server mapping. If possible, the request is forwarded to a dynamic origin server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11232: Session binding to origin server %s:%u (id=%d) for site %.*s is given up because the origin server is down.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11233: Retry-capable request is routed to origin server %s using load balancing.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11234: No defined origin server which does not exclude ESI fragments can serve this ESI fragment request for site %.*s. The request is dropped.
Cause: This request was for an ESI fragment and any site-to-server mapping which matched for host and URL excluded ESI fragments. Use of a dynamic origin server for this site could cause a loopback to this Oracle Web Cache. Therefore, a dynamic server will not be used for for this request.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11235: The request for site %.*s is dropped because no origin server for site pattern %s is available.
Cause: The origin server was not available.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11240: Origin server %s:%u (id=%d) has %d connections timed out or closed for other reasons.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11250: ESI include fragment protocol does not match origin server protocol: Origin Server Protocol=%s URL=%s%.*s%.*s
Cause: The protocol used in the src attribute does not match the protocol specified in the Sites page of Fusion Middleware Control. Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11260: Session binding cookie name %.*s with cookie value %.*s exceeds limit %d.
Cause: The cookie name and value exceeded the allowed length limit in Oracle Web Cache.
Action: Contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11261: Session binding query string parameter name %.*s with value %.*s exceeds limit %d.
Cause: The query string parameter name and value exceeded the allowed length limit in Oracle Web Cache.
Action: Contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11265: Starting dynamic origin server lookup (dispatcher %d entry %d)
Cause: Asynchronous dynamic origin server lookup started.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11266: Completed dynamic origin server lookup (dispatcher %d entry %d)
Cause: Asynchronous dynamic origin server lookup completed.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11270: Cache cluster member %s (id=%d) sent a peer member a configuration error in the response.
Cause: The response from a cache cluster member specified that its configuration did not match the configuration of a peer cache cluster member. This mismatch typically occurs because the configuration has not been propagated. You propagate configuration in the Cluster Operations page of Fusion Middleware Control.
Action: Contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11272: A response error from a cache cluster member is not from a known peer cache cluster member.
Cause: This error may be a logic error.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11290: DNS cache miss. Scheduling DNS task for host name %.*s
Cause: The entry for the host name was stale or missing in Oracle Web Cache's DNS cache. Oracle Web Cache scheduled a DNS task to get the host name.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11291: DNS lookup task scheduling fails for host %.*s.
Cause: Asynchronous task scheduling failed.
Action: Check the log of corresponding asynchronous task scheduling.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11292: DNS lookup succeeds for host %.*s.
Cause: The DNS cache miss and lookup succeeded.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11293: Oracle Web Cache fails to connect to dynamic origin server for ESI provider site and again performs a DNS lookup for host %.*s.
Cause: There was a possible stale DNS cache entry.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11294: Oracle Web Cache fails to connect to a dynamic origin server for ESI provider site with fresh DNS lookup result for host %.*s.
Cause: There was a potential system DNS error or invalid host.
Action: 1. Check whether the host is valid. 2. In a deployment environment, try to connect to this host and port. If the connection succeeds, then check the system/network DNS setup. 3. If problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11295: Oracle Web Cache failed in DNS lookup for host %.*s.
Cause: There was a potential system DNS error or invalid host.
Action: 1. Check whether the host is valid. 2. In a deployment environment, try to connect to this host and port. If the connection succeeds, then check the system/network DNS setup. 3. If problem persists, contact Oracle Support

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11296: Dynamic origin server name %.*s is too long.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11297: Cached DNS look up result for host %.*s is used.
Cause: Cached DNS look up result was used to establish a connection to a dynamic origin server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11298: The request is dropped because no routing relationship is configured for serving the content.
Cause: No routing relationship is configured.
Action: Configure the routing relationships approriately.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11299: The DMS ECID %.*s detected in origin server response
Cause: The ECID generated internally by Oracle Web Cache was identified as mapping to the DMS ECID discovered in the incoming X-Oracle-DMS-ECID" origin server response header.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11300: The attempt to create an entry in the cache failed due to low memory.
Cause: Memory low during insertion.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11301: Compose key failed for slave object in file %s line %s.
Cause: Population_ComposeKeyIfCacheable() return invalid values.
Action: No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11302: No I/O vector is found at line %d file %s.
Cause: tagInfo.nTotalNumberOfTags <= 0 && numDataBuffer > 0 for docBufList.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11303: Request method is not GET nor POST nor PUT; tunneling.
Cause: The HTTP method in the request is not one of GET, POST or PUT. Oracle Web Cache will tunnel this request between the client and the origin server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11304: Cache miss request.
Cause: The cache did not have a object matching the request.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11306: Request is for a non-cacheable object, forwarding request to the backend.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11308: Request may not be cacheable according to caching rule.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11311: Oracle Web Cache generates a HTTP 200 OK status code.
Cause: The request completed successfully.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11312: invalid Oracle-ECID request header
Cause: Oracle Web Cache was unable to parse the Oracle-ECID request header.
Action: Correct the syntax of the Oracle-ECID request header.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11313: The cache server reached the maximum number of allowed incoming connections. Listening is temporarily suspended on port %d.
Cause: The cache server reached the maximum number of incoming connections specified in the Resource Limits page of Fusion Middleware Control.
Action: Try again later. If this message persists, increase the maximum incoming connections in the Resource Limits page of Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11314: Listening has resumed on port %d.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11315: Oracle Web Cache generates a HTTP 202 Accepted status code.
Cause: The request was accepted.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11316: The request is for a End-User Performance Monitoring GIF file.
Cause: Normal activity for End-User Performance Monitoring.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11317: Oracle Web Cache generates an HTTP 304 Not-Modified status code.
Cause: Oracle Web Cache sent an HTTP 304 Not-Modified status code to the browser.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11321: Connection from browser cannot be established.
Cause: The handshake with the browser failed.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11322: Illegal value %d returned at frontend state machine.
Cause: Invalid status for Serv_HandleConn_DoGetRequest.
Action: No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11324: Function Serv_HandleConn_x is called with invalid state %d.
Cause: Unknown state in Serv_HandleConn_x.
Action: No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11325: Bad socket count
Cause: The socket count was inconsistent.
Action: No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11327: The request contains incorrect content.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11328: Invalid socket
Cause: Invalid socket was found.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11330: The request prefix %.*s%.*s matches an alias for configured site %.*s.
Cause: The alias for the site matched the Host request header.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11331: Request matches configured site:
Cause: The Host request header matched the site name.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11332: Failed to rewrite URI from '%.*s' to '%.*s' according to rewrite rule '%.*s'. The original URI will be used.
Cause: URI rewrite failed. Oracle Web Cache will use the original URI in subsequent operations without rewriting.
Action: Modify URL rewrite rules.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11333: URI is rewritten from %.*s to %.*s according to rewrite rule %.*s.
Cause: URI rewrite was successful.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11334: User-Agent request header %.*s does not match any rule. Oracle Web Cache remapped User-Agent to the default value %.*s.
Cause: User-Agent request header did not match any rule.
Action: Manually modify user-agent rules in the webcache.xml file.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11335: User-Agent request header remapped from %.*s to %.*s according to mapping rule %s.
Cause: User-Agent request header matched a rule.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11336: The request fails authorization check.
Cause: The request was not processed due to insufficient privileges or authorization rejection.
Action: Make sure you are authorized to perform the administration, invalidation or monitoring operation.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11337: Administration service unavailable. Try again later.
Cause: There were too many administration requests.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Ensure that only one user is the administrator user.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11338: URL is in the cache
Cause: There was a matching entry in the cache for this request.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11339: Oracle Web Cache determined the request might be cacheable based on existing cache policy.
Cause: There was no matching cache entry for this request. However, based on existing cache policy, Oracle Web Cache determined that it is likely to be cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11340: A new entry in the cache is created.
Cause: Oracle Web Cache created an entry in the cache for this request.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11342: Oracle Web Cache determined the request might not be cacheable based on existing cache policy.
Cause: There was no matching cache entry for this request. However, based on existing cache policy, Oracle Web Cache determined that it is likely to be not cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11343: The requested site does not have a matching origin server mapping. A bad request error will be returned.
Cause: There was no matching site-to-server mapping for this non-ESI-fragment request.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11344: Returning a freshly cached object.
Cause: The cached object will be returned because it is still fresh.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11345: The cached object is stale and this request will be served stale.
Cause: The cached object is stale and Oracle Web Cache decided to serve the stale copy to the request.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11346: The cached object is stale and an origin server will be contacted for a fresh copy.
Cause: Because the cached object is stale, Oracle 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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11347: The cached object is garbage.
Cause: The cached object is in garbage state, meaning that it could not be used to serve to the client.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-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.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11349: The request will be forwarded to the origin server to obtain a fresh copy of the object.
Cause: The cached object was in garbage state, and there was no other request pending to update the cache. Oracle 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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11350: The request contains no site information in the URL or Host header. The configuration of the default site %s will be used.
Cause: The request did not contain a Host header, nor did it have an absolute URL that contained a site name. Oracle Web Cache will use the default site in the configuration for this request.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11351: The complete site name is: %s
Cause: The complete site name was resolved based on the configuration.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11352: There is no matching defined site or aliases in the configuration for this request.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11354: Out of memory while processing the request. A service unavailable response is returned to the client. Client IP: %s
Cause: Oracle Web Cache failed to obtain enough memory while processing the request.
Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11355: Single request header length exceeds configured maximum. A forbidden error response is returned to the client. Client IP: %s
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 Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11356: Total request header length exceeds configured maximum. A forbidden error response is returned to the client. Client IP: %s
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 Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11357: Failed to resolve the requested site name. A bad host error response is returned to the client.
Cause: The request did not contain enough information about the site name.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11358: Failed client certificate check. A forbidden error response is returned.
Cause: The request was for a URL that requires a client certificate, and the certificate check failed for this request.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11359: Host header missing in HTTP/1.1 request. A bad host error response is returned.
Cause: The request was an HTTP/1.1 request, but is missing the required Host header.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11360: Error processing the Transfer-Encoding header in the request. A bad request error response is returned.
Cause: An error was encountered while processing the Transfer-Encoding header in the request.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11361: Transfer-Encoding specified in the request is not supported. An HTTP not implemented error response is returned.
Cause: Oracle Web Cache only supports chunked encoding. Other types transfer encoding are not supported.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11362: Malformed request. A bad request error response is returned. Client IP: %s
Cause: The request was malformed.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11363: Out of memory while processing the request. The request is dropped.
Cause: Oracle Web Cache failed to obtain enough memory while processing the request.
Action: Adjust the maximum cache size in the Resource Limits page of Fusioin Middleware Control. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Memory

WXE-11364: Network error response is returned.
Cause: A network error was encountered while processing the request.
Action: Check other error messages related to this request.

Level: 16

Type: ERROR

Impact: Network

WXE-11365: Server busy response is returned.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11366: A client connection to listening port %d is dropped.
Cause: A connection failure was encountered between Oracle Web Cache and the client, so the request could not be completed.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11367: No matching origin server can be found for the requested site. A bad host error response is returned
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 Oracle Web Cache Manager.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11368: ESI exception error response is returned.
Cause: An ESI exception was encountered while processing the request.
Action: Check other error messages related to this request.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11369: The request method is not supported. An HTTP not implemented error response is returned.
Cause: The request specified an unsupported method.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11370: A chunk-encoded request entity body contains a chunk that exceeds %u bytes. A bad request error response is returned. Client IP: %s
Cause: This chunk-encoded request contained a chunk that exceeded the DOCHEADERBUFFERSIZE setting in internal.xml
Action: Consider increasing DOCHEADERBUFFERSIZE.

Level: 16

Type: ERROR

Impact: Requests/Responses

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

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11372: Aborting origin server request
Cause: A request sent to Oracle Web Cache was aborted. Because Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11373: This request %.*s is not being enabled with End-User Performance Monitoring
Cause: A single response from the origin server to Oracle Web Cache was not enabled for End-User Performance Monitoring because of a software limitation.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-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
Cause: The cached object is stale and Oracle 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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11377: Aborting receiving request entity body because origin server connection has been aborted
Cause: An error occurred while sending the request entity body to an origin server. The origin server connection was aborted. Because of this, Oracle Web Cache is aborting the request received from the client.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11379: The request is using global site configuration.
Cause: Oracle Web Cache used global site configuration for this request.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11381: A request is sent for a forbidden operation.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11382: The URL for the statistics monitoring request is not valid.
Cause: The incorrect URL was used for the statistics monitoring request.
Action: Check the URL.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11383: The request has an internal error.
Cause: The request was invalid.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11384: Changing incoming ECID from %.*s to %.*s
Cause: The ECID discovered in the incoming Oracle-ECID request header has been changed to reflect the nested client request.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11385: The request fails because the service is unavailable.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11386: The request fails because the portal service is unavailable.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11387: The request fails due to a gateway timeout.
Cause: The request was not be processed due to a gateway timeout.
Action: Make sure the gateway is active and available for processing requests.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11388: The DMS ECID %.*s overrides the legacy ECID %s.
Cause: The ECID generated internally by Oracle Web Cache was identified as mapping to the DMS ECID discovered in the incoming ECID-Context" client request header.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11389: The request fails due to unsupported ESI operation.
Cause: The request was not processed because no clients on the path of request can provide sufficient ESI processing capability.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the offending ESI tag for correctness or possible typographical errors.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11390: The ECID %.*s overrides the temporary ECID %s.
Cause: The ECID generated internally by Oracle 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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11391: Detailed information about ECID %s is in the next line.
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.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11392: The object is in the cache, but the inactivity timeout cookie must be updated.
Cause: The cached object will be returned to the client, but the inactivity timeout cookie must first be updated.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11393: The central cache or provider cache has challenged the remote or subscriber cache for identity information.
Cause: The central cache or provider cache requested content from its parent cache. Before receiving content, it must register itself as an Oracle Web Cache to establish a hierarchical relationship.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11394: The invalidation request is redundant.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11396: unknown internal error
Cause: The error number was improperly set.
Action: Check which module is not setting the error number

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11397: request failed due to insufficient memory
Cause: The object request failed due to insufficient memory necessary to process all of the objects.
Action: Increase the size of the pagefile.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11398: A client connection to listening port %d is dropped at the end of keep-alive session.
Cause: A connection between Oracle Web Cache and the client was terminated, marking the end of the keep-alive session.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11399: The port number in the Host header %.*s is replaced with the port number of the connection %.*s.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11400: non-200 OK HTTP status code response code of %d
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11403: begin cacheability decision for url:
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11404: Time %.*s in the Last-Modified header is after the current time. The cache is using the current time instead.
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 Oracle Web Cache is running has its clock in-sync with the clock of the application Web server.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11405: Request/Response matches no-cache rule with URL expression \"%s\".
Cause: The request URL matched a non-cacheable caching rule.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11406: Request/Response matches no-cache rule with MIME type expression \"%s\".
Cause: The request/response matched a non-cacheable caching rule.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11407: Request/Response matches no-cache rule with URL expression \"%s\" and MIME type expression \"%.*s\".
Cause: The request/response matched a non-cacheable caching rule.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11408: Request/Response matches no-cache catch-all rule.
Cause: The request/response matched a non-cacheable caching rule.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11409: HTTP POST request body length %d exceeds maximum cacheable post body limit %d.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11410: Response contains cookie \"%.*s=%.*s\", which is not present in the request.
Cause: The response received from the origin server contained a newly created cookie that was not present in the request. As a result, Oracle Web Cache considered the response to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11411: Response contains cookie \"%.*s=%.*s\", which does not match the same cookie value \"%.*s\" in the request.
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, Oracle Web Cache considered the response to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-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.
Cause: The Surrogate-Control header in the response contained control directives that were in conflict with an existing caching rule. This will cause Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11413: The HTTP request method is not GET, or the URL contains query string parameters. The request is not cacheable.
Cause: The request used an HTTP method that was neither GET nor POST. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11414: Basic cache key is composed with sitename %.*s, URI %.*s, method %.*s, post body %.*s.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11415: Final cache key is composed sitename %.*s, URI %.*s, method %.*s, post body %.*s, multiversion %.*s, compressed %.*s.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11416: The response is considered not cacheable due to the lack of caching directives.
Cause: The response did not contain any headers with caching directives and had no matching caching rule. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11417: URL is not cacheable based on its HTTP headers.
Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11418: The response contains a Surrogate-Control header with either a no-store control directive or a zero-value max-age control directive, indicating that the response is non-cacheable.
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, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11419: The Surrogate-Control header contains a nonzero max-age=%d+%d control directive, indicating that the response is cacheable.
Cause: The response contained a Surrogate-Control header with a nonzero max-age directive. As a result, Oracle Web Cache considered it to be cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11420: The response contains Surrogate-Control header with a zero-value max-age control directive and ETag header, indicating that the response is cacheable with validation.
Cause: The response contained Surrogate-Control header with a zero-value max-age control directive and ETag header. As a result, Oracle Web Cache considered it to be cacheable with validation.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11421: The response contains ETag and X-Oracle-Cache headers, indicating that the response is cacheable with validation.
Cause: The response contained ETag and X-Oracle-Cache headers. As a result, Oracle Web Cache considered it to be cacheable with validation.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11422: The Surrogate-Control header contains the vary control directive, overriding configuration.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11423: Oracle Web Cache ran out of memory while creating caching rule according to the vary control directive of the Surrogate-Control header.
Cause: There was not sufficient memory for Oracle Web Cache to process the vary control directive.
Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11424: The request contains session %s, which makes it non-cacheable based on the existing caching rule.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11425: The request does not contain session %s, which makes it non-cacheable based on the existing caching rule.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11426: The request does not contain cookie %s, which makes it non-cacheable based on the existing caching rule.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11427: The request does not contain HTTP request header %s, which makes it non-cacheable based on the existing caching rule.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11428: The X-Oracle-Expires header contains TTL of %d seconds, indicating that the response is cacheable.
Cause: The response contained an X-Oracle-Expires header with a nonzero TTL value. As a result, Oracle Web Cache considered it to be cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11429: The response contains ETag header and zero value TTL in X-Oracle-Expires header, indicating that the response is cacheable with validation.
Cause: The response contained an X-Oracle-Expires header with a zero value TTL and an ETag header. As a result, Oracle Web Cache considered it to be cacheable with validation.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11430: The response contains zero value TTL in X-Oracle-Expires header with no ETag header, indicating that the response is non-cacheable.
Cause: The response contained an X-Oracle-Expires header with a zero value TTL. As a result, Oracle Web Cache considered it to be not cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11431: In absence of any overriding headers in the response, the response is not cacheable based on the existing caching rule.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11432: The HTTP response headers indicate that the response is cacheable.
Cause: The response contained the HTTP headers that indicate it is cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11433: An existing NCM entry states object is too large to be cacheable.
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 page of Fusion Middleware Control.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11434: The ESI include or inline tag for this fragment contains reference TTL=%d+%d, making the fragment cacheable.
Cause: The ESI include or inline tag for the fragment contained a nonzero reference TTL. As a result, Oracle Web Cache considered the fragment cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11442: Oracle Web Cache could not process the response for ESI because the Content-Type is not valid for ESI processing.
Cause: The Surrogate-Control response header contained a content token with values indicating that ESI parsing should be done, but the Content-Type header value was not text or HTML.
Action: If the content needs to be processed for ESI, the application code must modify the Content-Type to be text or HTML.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11443: The request does not contain header %.*s, which makes it non-cacheable based on the vary control directive in the Surrogate-Control response header.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11444: The request does not contain cookie %.*s, which makes it non-cacheable based on the vary control directive in the Surrogate-Control response header.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11445: Following URL will not be cached:
Cause: The final cacheability decision for this response is not cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11446: URL which will be cached is:
Cause: The final cacheability decision for this response is cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11447: Request/Response matches a dynamic caching rule.
Cause: The request/response matched a dynamic caching rule.
Action: No action required. caching rules.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11448: Request/Response does not match any caching rule.
Cause: The request/response did not match any configured caching rule.
Action: If this is not the intended behavior, then check the configured caching rules.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11449: The response is too large to be cached.
Cause: The response size is larger than the configured maximum size of a single cached object.
Action: Check the configured Maximum Size of Single Cached Object in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11450: Object is cached because it does not exceed allowed size for an object.
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11451: Update fails because object is no longer cacheable.
Cause: This request was no longer cacheable.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11452: Update fails; Oracle Web Cache fetches response as a cache miss.
Cause: An update of the object failed. Oracle Web Cache processes the request as a cache miss.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11453: A new cache policy is created based on the Surrogate-Control header.
Cause: The caching properties specified in the Surrogate-Control header conflicts with the existing cache policy, therefore Oracle 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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11454: Current compression is on, conflicting with the previous setting.
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 Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11455: The response indicates security validation is required, conflicting with the previous setting.
Cause: The response contains a security validation setting either explicitly through the Surrogate-Control: secure-view token or implicitly through the absence of it that was in conflict with an existing security validation setting. This will cause Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11456: The response indicates version validation is required, conflicting with the previous setting.
Cause: The response contains a version validation setting either explicitly through the Surrogate-Control: version token or implicitly through the absence of it that was in conflict with an existing security validation setting. This will cause Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11457: The response contains a Surrogate-Control: authentication token that is not supported by Oracle Web Cache.
Cause: The Surrogate-Control: authentication token value of response header indicates an authentication mechanism that is not supported by Oracle Web Cache for caching such documents. The response will not be cached.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If this is not the intended behavior, then check the application logic.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11458: Following URL that requires Oracle Single Sign-On authentication is being inserted in the cache:
Cause: Caching is enabled for documents that require Oracle Single Sign-On authentication but have no other authorization requirement.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11459: URL is not cacheable because the request contains an Authorization header.
Cause: The request contained a HTTP header that indicated the response would be non-cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11460: URL is not cacheable because the request contains a Proxy-Authorization header.
Cause: The request contained a HTTP header that indicated the response would be non-cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11461: URL is not cacheable because the request contains a Cookie header.
Cause: The request contained a HTTP header that indicated the response would be non-cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11462: URL is not cacheable because the response contains a Set-Cookie header.
Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11463: URL is not cacheable because the response contains a Cache-Control: no-store header.
Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11464: URL is not cacheable because the response contains a Cache-Control: no-cache header.
Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11465: URL is not cacheable because the response contains a Pragma: no-cache header.
Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11466: URL is not cacheable because the response contains a Warning header.
Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11467: URL is not cacheable because the Expires header indicates that it has expired.
Cause: The response contained regular HTTP headers that indicated it was not cacheable. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11468: URL is not cacheable because the response contains no expiration information.
Cause: The response contained no expiration headers. As a result, Oracle Web Cache considered it to be non-cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11469: URL is cacheable because the response contains an ETag header.
Cause: The response contained HTTP headers that indicate it is cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11470: URL is cacheable because the response contains an Expires header, indicating it expires in the future.
Cause: The response contained HTTP headers that indicate it is cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11471: URL is cacheable because the response contains a Cache-Control header with a positive max-age directive.
Cause: The response contained HTTP headers that indicate it is cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11472: The response contains a Surrogate-Control header with a restore-POST directive, indicating that the response is not cacheable.
Cause: The response contained instructions to cache the request POST data content. As a result, Oracle Web Cache considered the response to be non cacheable. If this is a 302 redirect to a POST response, Oracle Web Cache will save the the request POST content in the cache to be used upon a future restore POST request.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11473: Cache key output truncated due to excessive post body size
Cause: The cache key message (11414, 11415) could not display the entire cache key because the post body message size exceeded the threshold specified in the configuration file.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11474: Current compression is off, conflicting with the previous setting.
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 Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11475: Current SSO authentication is on, conflicting with the previous setting.
Cause: The response contains an authentication setting either explicitly through the Surrogate-Control header or implicitly through the absence of it that was in conflict with an existing authentication setting. This will cause Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11476: Current SSO authentication is off, conflicting with the previous setting.
Cause: The response contains an authentication setting either explicitly through the Surrogate-Control header or implicitly through the absence of it that was in conflict with an existing authentication setting. This will cause Oracle 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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11477: The response contains a Surrogate-Control: authentication token but SSO authentication is not enabled.
Cause: The Surrogate-Control: authentication token is present but SSO authentication is not enabled for caching. The response will not be cached.
Action: Turn on SSO authentication by editing webcache.xml: find the SECURITY element under the GENERAL element. Assign a positive value to the SSO_COOKIE_CACHE_TIME attribute.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11478: The response indicates security validation is not required, conflicting with the previous setting.
Cause: The response contains a security validation setting either explicitly through the Surrogate-Control: secure-view token or implicitly through the absence of it that was in conflict with an existing security validation setting. This will cause Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11479: The response indicates version validation is not required, conflicting with the previous setting.
Cause: The response contains a version validation setting either explicitly through the Surrogate-Control: version token or implicitly through the absence of it that was in conflict with an existing security validation setting. This will cause Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11480: Post body masked due to security
Cause: The cache key message (11414, 11415) will not display the entire cache key because the post body was masked.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11481: Request/Response matches caching rule with URL expression \"%s\".
Cause: The request/response matched a cacheable caching rule.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11482: Request/Response matches caching rule with MIME type expression \"%.*s\".
Cause: The request/response matched a cacheable caching rule.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11483: Request/Response matches caching rule with URL expression \"%s\" and MIME type expression \"%.*s\".
Cause: The request/response matched a cacheable caching rule.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11484: Request/Response matches catch-all caching rule.
Cause: The request/response matched a cacheable caching rule.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11485: Request/Response matches disabled caching rule with URL expression \"%s\".
Cause: The request/response matched a disabled caching rule; thus, the rule is ignored.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11486: Request/Response matches disabled caching rule with MIME type expression \"%.*s\".
Cause: The request/response matched a disabled caching rule; thus, the rule is ignored.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11487: Request/Response matches disabled caching rule with URL expression \"%s\" and MIME type expression \"%.*s\".
Cause: The request/response matched a disabled caching rule; thus, the rule is ignored.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11488: Request/Response matches disabled catch-all caching rule.
Cause: The request/response matched a disabled caching rule; thus, the rule is ignored.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11489: HTTP response-header parsing error on Surrogate-Control token: %.*s. Full header line is: %.*s.
Cause: An HTTP Surrogate-Control response header from the origin server contained an individual header value that was malformed or unexpected. The Surrogate-Control tokens up to the malformed one were processed. The malformed token and any tokens which follow it were ignored.
Action: If the behavior is still as expected, no action is required. If the behavior is not as expected, check the application code that generates the Surrogate-Control header.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11500: StatisticsTimerInterval configuration parameter should be between 10, 000 and 1, 000, 000 microseconds, and should be a factor of 1, 000, 000
Cause: Illegal configuration parameter for statistics timer interval.
Action: This error usually occurs as a result of wrong configuration. Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11501: While getting detailed memory statistics, pointer swapped while filling HTML
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.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11502: Unable to create or open file %s for write. Cache contents not written.
Cause: The cache server was unable to open the file specified. Either the file already exists and the Oracle Web Cache user does not have write permission on the file or the Oracle 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 Oracle Web Cache to create the file or write to it.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11503: Abnormal statistics value of %s was detected. Value 0 was recorded.
Cause: Internal error. The statistics value that was returned was an abnormal (negative) value.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11504: Client IP checking for the statistics message fails. Access denied.
Cause: Oracle 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 Fusion Middleware Control.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11505: The number of statistics monitoring requests exceeds queue limit.
Cause: The number of statistics monitoring requests exceeded the request queue limit.
Action: Try the request at a later time.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11506: Invalid IP address in statistics request
Cause: The request to the statistics port is from invalid IP address.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11600: Illegal value set for HeuristicsValidityFunc
Cause: The heuristics validity function ID was corrupted. This error is the result of internal configuration errors.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11601: Illegal value set for HeuristicsPropensityFunc
Cause: The heuristics propensity function ID was corrupted. This error is the result of internal configuration errors.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11602: Illegal value set for HeuristicsThresholdFunc
Cause: The heuristics threshold function ID was corrupted.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. This error usually occurs as a result of internal configuration errors. If the problem persists, contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11604: Illegal value set for POPULARITYSCALE.
Cause: The popularity heuristic parameter is not valid.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11605: Illegal value set for THRESHOLDSCALE.
Cause: The threshold heuristic parameter is not valid.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11606: Illegal value set for THRESHOLDBASE.
Cause: The threshold base heuristic parameter is not valid.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11608: Illegal value set for ECATELMFACTOR.
Cause: The Cate LMFactor heuristic parameter is not valid.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11610: Illegal value set for OWNERSHIPPREFERENCE.
Cause: The ownership preference heuristic parameter is not valid.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11700: Client IP checking for the invalidation message fails. Access denied.
Cause: Oracle 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 Fusion Middleware Control.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11701: Authentication failed. Invalid username or password.
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 Fusion Middleware Control.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11702: The invalidation request contains an empty request body.
Cause: The invalidation request contained an empty request body.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Resend the invalidation request with a request body.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11703: Invalidation request specifies a wrong URL.
Cause: The invalidation message carried a wrong request URL.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11704: Invalidation message contains XML parsing errors.
Cause: The invalidation message contained invalid XML.
Action: Correct the XML errors in the invalidation message.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11705: Invalid validity level '%s' is requested.
Cause: The invalidation message specified an invalid validity level. The correct range of level is between 0 and 9.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the message to use a validity level between 0 to 9.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11706: %d object(s) matching prefix '%s' are invalidated.
Cause: Invalidation of objects was successful.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11707: Object with URL '%s' is successfully invalidated.
Cause: Invalidation was successful.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11708: Object with URL '%s' is not cacheable. Invalidation is not done.
Cause: The URL was not a cacheable object. Invalidation is not performed for non-cacheable objects.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11710: Object with URL '%s' not in the cache. Invalidation is not performed.
Cause: The object was not in the cache. Invalidation is not performed for non-cacheable objects.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11711: Oracle Web Cache cannot compose key pattern for requested URL '%s'.
Cause: Oracle Web Cache could not compose a key pattern for requested URL expression.
Action: Correct the URL expression in the invalidation message.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11712: Invalidation message contains unrecognized cookies.
Cause: The invalidation message contained nonexistent cookies.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the cookie name specified in the invalidation message.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11713: Invalid regular expression found in invalidation message. %s
Cause: The invalidation message contained an invalid regular expression that could not be compiled.
Action: Correct the regular expression in the invalidation message.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11715: Regular expression matching error. Error number: %d
Cause: The regular expression in the invalidation message was invalid. Oracle Web Cache could not perform regular expression matching successfully.
Action: Check regexec man page with the error number for syntax error description.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11716: Invalidation XML message cannot be parsed.
Cause: Invalidation XML message could not be parsed.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11717: Invalidation XML error found in invalidation message.
Cause: Oracle 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".

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11718: Cannot allocate memory for KeyParam structure.
Cause: Oracle Web Cache could not allocate memory for KeyParam structure.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check memory configuration. Restart Oracle Web Cache if necessary.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11719: Cannot allocate memory for Invalidate_AttributeT structure.
Cause: Oracle Web Cache could not allocate memory for Invalidate_AttributeT structure.
Action: Check memory configuration. Restart Oracle Web Cache if necessary.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11720: Cannot allocate memory for or sizeof '%s'.
Cause: Oracle Web Cache could not allocate memory.
Action: Check memory configuration. Restart Oracle Web Cache if necessary.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11721: Cannot read value for XML element/attribute: '%s'.
Cause: Oracle Web Cache was unable to obtain all information about the specified XML element or attribute.
Action: Correct the XML in the invalidation message.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11722: Invalidation message specifies unknown version: '%s'.
Cause: The invalidation message specified an unknown version.
Action: Correct the invalidation message to use version "WCS-1.1 or "WCS-1.0".

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11723: Value of XML string '%s' too long. Actual length: %d, max length allowed: %d.
Cause: The XML string in the invalidation message exceeded the allowed length limit.
Action: Correct the XML in the invalidation message.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11724: URL path prefix does not end with '/': '%s'.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11725: Cannot create XML element/attribute: '%s'.
Cause: Oracle Web Cache could not create the XML element or attribute.
Action: Check the maximum cache size in the Resource Limits page of Fusion Middlewae Control. Restart Oracle Web Cache if necessary.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11726: Cannot set XML attribute '%s' for element '%s'.
Cause: Oracle Web Cache could not set the XML attribute value.
Action: Check the maximum cache size in the Resource Limits page of Fusion Middleware Control. Restart Oracle Web Cache if necessary.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11727: Unexpected/unsupported argument '%s' in function '%s'.
Cause: The invalidation message specified an unsupported name and value pair for <SYSTEMINFO ... />
Action: See Chapter "Sending Invalidation Requests" in the Oracle Web Cache Administrator's Guide for the possible values allowed for <SYSTEMINFO ... />.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11728: Cluster error: Peer cache '%d' returns bad response.
Cause: The invalidation response from a peer cache was not parsed.
Action: Check the network connection between current cache and its peer.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11729: Invalidation message contains conflicting HOST values: '%s' and '%s'.
Cause: The invalidation message contained conflicting HOST values in the URIPREFIX and the HOST attributes.
Action: Correct the host information in the invalidation message.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11730: Invalidation message from provider cache with IP %s port %d is dropped.
Cause: The invalidation message propagated from the specified provider cache is either outdated or invalid. Invalidation is discarded.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11731: Normal request is from an unknown Oracle Web Cache: IP %s port %s.
Cause: The invalidation message was propagated from an unknown cache. Invalidation is discarded.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11732: Invalidation contains host name '%s' which does not match the IP '%s' from which invalidation comes.
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: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the host information in the invalidation message.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11733: Invalidation object is ignored due to lack of host information.
Cause: Invalidation propagated from a cache does not specify a host name in the URIPREFIX or HOST attribute of the message.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the host information in the invalidation message.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11734: Invalidation sent to subscriber cache with IP %s port %d has returned with response code: '%s'.
Cause: The provider cache response was received.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11735: Subscriber cache with IP %s port %d is removed due to an exceeded failure count. Total subscriber(s): %d.
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.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11736: Failed to start fiber to send invalidation to subscriber cache with IP %s port %d.
Cause: Oracle Web Cache failed to send invalidation. to subscriber cache.
Action: Check the configuration file. Restart Oracle Web Cache if necessary.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11737: Invalidation message may be lost from provider cache with IP %s port %d.
Cause: The subscriber cache missed an invalidation message from the provider cache. All objects are invalidated.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11738: Provider cache fails in propagating invalidation message to subscriber cache.
Cause: The provider cache failed in propagating the invalidation message to subscriber cache.
Action: Check the configuration file. Restart Oracle Web Cache if necessary.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11740: Invalidation message contains too many cookies, headers, or attributes. Maximum allowed is '%d'.
Cause: Invalidation message contained too many cookies, headers, or attributes. Invalidation was not performed.
Action: Rephrase the invalidation message.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11748: Invalidation with INFO '%s' has returned with status '%s'; number of objects invalidated: '%d'.
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.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11750: Invalid syntax for the value of QUERYSTRING_PARAMETER in invalidation message:'%s'.
Cause: The invalidation message contained invalid syntax in the QUERYSTRING_PARAMETER value.
Action: Correct the error in invalidation message.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11752: Cannot decode %s with value '%s', therefore decoding is not done.
Cause: Cannot decode XML value specified. The original value is used.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11754: Cannot allocate new XML context for invalidation.
Cause: Oracle Web Cache could not create XML context for invalidation.
Action: Check memory resources on the machine. Reinstall Oracle Web Cache if necessary.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11755: Default URL size is too small for cache key.
Cause: Default URL size was too small for cache key.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11757: Unsupported OTHER element specified in invalidation message: name='%s', type='%s', value='%s'.
Cause: Unsupported OTHER element was specified in the invalidation message.
Action: See Chapter "Sending Invalidation Requests" in the Oracle Web Cache Administrator's Guide for all supported OTHER elements.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11761: Site %.*s has no matching site definition and thus cannot be verified.
Cause: Response header invalidation failed because the site specified in the original request does not have a corresponding site definition with which to verify the invalidation response header.
Action: Create an appropriate site definition.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11762: Syntactically incorrect URI, '%.*s', specified in invalidation response header.
Cause: Response header invalidation failed because the URI in the invalidation response header was not syntactically valid.
Action: Change application to only append invalidation response headers with valid URIs.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11763: URI, '%.*s', specified in invalidation response header does not match incoming request's site definition.
Cause: Response header invalidation failed because the URI in the invalidation response header did not match the site specified in the original request.
Action: Change application to only append invalidation response headers whose site matches that of the incoming request.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11764: Unable to open connection to invalidation port of peer cache member \"%s\" because its state is not Ready.
Cause: The invalidation port of the peer cache member is not ready to accept connections.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11800: CGI communication error.
Cause: Network I/O error while communicating with CGI application.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11802: Cannot open Service Manager: %s
Cause: The admin server was unable open the Windows Service Manager.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11803: Cannot open Windows Service %s: %s
Cause: The admin server was unable to open the specified service.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11804: Cannot obtain the system status for Windows service %s: %s
Cause: The admin server was unable to retrieve the status for the specified service.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11805: Cannot control service %s: %s
Cause: The admin server was unable to start or stop the specified Windows service.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11806: Cannot stop service %s
Cause: The admin server failed to stop the specified service.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11807: Windows service, %s, stopped
Cause: The admin server has successfully stopped the specified service.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-11809: The admin server could not start the cache server, running in admin-only mode: %s
Cause: The admin server was unable to start the cache server.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Review the error log file or use the Event Viewer to help determine the cause of the problem.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11810: Cannot start Auto-Restart. %s does not exist
Cause: Unable to find the specified Auto-Restart executable.
Action: Restore the Auto-Restart executable, webcachemon, to its proper location, which is the Oracle Web Cache bin directory.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11811: Unable to fork a new process for starting Auto-Restart.
Cause: Oracle 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.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11812: Auto-Restart did not start. An error code was returned.
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.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11813: Cannot start service %s
Cause: The admin server failed to start the specified service.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11814: Logging info: %s
Cause: An error is logged.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Refer to the logged error details and take the appropriate action.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11815: The admin server process is unable to determine the OPMN auto-restart setting. Error reading or parsing %s
Cause: An error occurred while the admin server process was attempting to obtain the restart setting for Oracle Web Cache in the OPMN XML configuration file, opmn.xml.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11816: Error while changing the OPMN auto-restart setting for Oracle Web Cache. Command: %s. Return code: %d. Command output: %s
Cause: An error occurred while trying to execute the command specified. Oracle Web Cache uses this command to change the restart setting in the OPMN XML configuration file, opmn.xml.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Execute the command manually.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11817: Unable to allocate or access a shared memory segment of size %u bytes. %s(): %s
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 message is no longer used as of Oracle Fusion Middleware 11g. This error usually occurs as a result of insufficient system resources. Refer to the included operating system level error message for further information.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11818: Login attempt fails to admin server process.
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11819: Unable to open temporary file %s
Cause: The admin server was unable to create a temporary file used during the processing of new configuration changes.
Action: No action required

Level: 1

Type: WARNING

Impact: Files

WXE-11901: SSL context creation failed, NZE-%d
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.

Level: 1

Type: ERROR

Impact: Security

WXE-11902: SSL configuration fails, NZE-%d
Cause: SSL library configuration failed.
Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

Level: 1

Type: WARNING

Impact: Security

WXE-11903: SSL set credential fails, NZE-%d
Cause: SSL library failed to set credentials.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

Level: 1

Type: WARNING

Impact: Security

WXE-11904: SSL handshake fails NZE-%d
Cause: SSL handshake error occurred.
Action: See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

Level: 16

Type: ERROR

Impact: Security

WXE-11905: SSL additional information: %.*s
Cause: This message provides additional diagnostic information about the preceeding SSL error.
Action: No action required.

Level: 1

Type: WARNING

Impact: Security

WXE-11907: The server cannot allocate memory while in %s.
Cause: The system has run out of memory.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Restart the system and Oracle Web Cache.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11908: SSL set peerid fails, NZE-%d
Cause: SSL library failed to create SSL Session
Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

Level: 1

Type: WARNING

Impact: Security

WXE-11909: getpeername fails during SSL handshake, system error %d
Cause: Could not determine peer IP Address.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 1

Type: WARNING

Impact: Security

WXE-11910: failed to normalize Wallet Resource Locator (WRL) %s
Cause: WRL could not be parsed.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Confirm that the WRL is in the correct format.

Level: 1

Type: WARNING

Impact: Security

WXE-11912: unknown state in SSL session garbage collector
Cause: There is an unknown code bug.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Security

WXE-11913: SSL set hardware acceleration fails, NZE-%d.
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.

Level: 1

Type: ERROR

Impact: Security

WXE-11914: SSL set thread usage fails, NZE-%d.
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.

Level: 1

Type: WARNING

Impact: Security

WXE-11915: The SSL engine fails to initialize, NZE-%d.
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.

Level: 1

Type: ERROR

Impact: Security

WXE-11916: Oracle cryptographic toolkit context initialization fails, NZE-%d.
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.

Level: 1

Type: WARNING

Impact: Security

WXE-11917: SSL wallet %s file %s does not exist.
Cause: The wallet was not found in the wallet directory.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check for wallet file ewallet.p12 or ewallet.der in the wallet directory.

Level: 1

Type: WARNING

Impact: Security

WXE-11918: The SSL Wallet %s file %s is not readable.
Cause: The wallet was not readable by Oracle Web Cache.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the file system permissions on this file.

Level: 1

Type: WARNING

Impact: Security

WXE-11919: The SSL wallet auto-login file %s does not exist. Wallet does not appear to be auto-login wallet.
Cause: The wallet auto-login file cwallet.sso was not found.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check for wallet file cwallet.sso in wallet directory.

Level: 1

Type: WARNING

Impact: Security

WXE-11920: The SSL wallet auto-login file %s is not readable. Wallet does not appear to be auto-login wallet.
Cause: The wallet auto-login file cwallet.sso was not readable by Oracle Web Cache.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the file system permissions on this file.

Level: 1

Type: WARNING

Impact: Security

WXE-11921: The origin server wallet did not open. Operating without wallet for backend. Only Diffie-Hellman anonymous connections supported to origin servers.
Cause: Origin server wallet did not open or was not specified.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Without an origin server wallet, only Diffie-Hellman SSL Connections can be made.

Level: 1

Type: WARNING

Impact: Security

WXE-11922: %s wallet fails to open at location %s, NZE-%d, as user %s
Cause: The wallet could not be opened as the user specified.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check for the existence of the wallet and make sure auto-login was enables as the user specified.

Level: 1

Type: WARNING

Impact: Security

WXE-11923: %s wallet fails to open at location %s, NZE-%d.
Cause: The wallet could not be opened
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check for the existence of the wallet.

Level: 1

Type: WARNING

Impact: Security

WXE-11924: Oracle wallet fails to open persona, NZE-%d.
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.

Level: 1

Type: WARNING

Impact: Security

WXE-11925: No wallet configured with SSL; server initialization fails.
Cause: SSL was configured without specifying a wallet.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Correct the configuration file.

Level: 1

Type: ERROR

Impact: Security

WXE-11926: Oracle Web Cache fails to set cipher suite in SSL handshake, NZE-%d.
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.

Level: 1

Type: WARNING

Impact: Security

WXE-11927: Oracle Web Cache fails to get supported cipher suites, NZE-%d.
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.

Level: 1

Type: ERROR

Impact: Security

WXE-11928: Oracle Web Cache fails to set session reference, NZE-%d.
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.

Level: 1

Type: ERROR

Impact: Security

WXE-11929: SSL handshake fails NZE-%s.
Cause: SSL handshake error occurred.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. See the "Network Security Messages (NZE)" chapter of the Oracle Database Error Messages for information about NZE errors.

Level: 1

Type: WARNING

Impact: Security

WXE-11930: The object is in the cache, but Single Sign-On authentication is required.
Cause: The cached object will be served to the client, but Single Sign-On authentication must be done before the document is served.
Action: No action required.

Level: 1

Type: TRACE

Impact: Security

WXE-11931: The object is in the cache, but the inactivity timeout cookie must be updated.
Cause: The cached object will be served to the client, but the global inactivity timeout cookie must first be updated.
Action: No action required.

Level: 1

Type: TRACE

Impact: Security

WXE-11932: The request has a Single Sign-On authentication cookie validated by Oracle Web Cache.
Cause: The Single Sign-On authentication cookie associated with the request has been validated by Oracle Web Cache.
Action: No action required.

Level: 1

Type: TRACE

Impact: Security

WXE-11933: The request has a Single Sign-On authentication cookie that needs to be validated by origin server.
Cause: The Single Sign-On authentication cookie associated with the request needs to be validated by the origin server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Security

WXE-11934: The request has a global inactivity timeout cookie validated by Oracle Web Cache.
Cause: The global inactivity timeout cookie associated with the request has been validated by Oracle Web Cache.
Action: No action required.

Level: 1

Type: TRACE

Impact: Security

WXE-11935: The request has a global inactivity timeout cookie that needs to be validated by origin server.
Cause: The global inactivity timeout cookie associated with the request needs to be updated by the origin server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Security

WXE-11936: Oracle Web Cache has started watching for %.*s Single Sign-On authentication cookie.
Cause: Oracle Web Cache has received new Single Sign-On authentication cookie name settings from origin server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Security

WXE-11937: Oracle Web Cache has started watching for %.*s global inactivity timeout cookie.
Cause: Oracle Web Cache has received new global inactivity timeout cookie name settings from an origin server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Security

WXE-11938: A new %s cookie with key %llx:%llx stored in memory for %d seconds.
Cause: Oracle Web Cache has temporarily stored the cookie in memory.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11939: The %s cookie with key %llx:%llx and reference count %d in memory has been marked stale.
Cause: The cookie stored in memory has been marked stale for garbage collection.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11940: The %s cookie with key %llx:%llx is being removed from memory.
Cause: The stale cookie stored in memory is being garbage collected.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11941: Oracle-WebCache-OSSO response header contains token \"%.*s\" with unexpected value \"%.*s\".
Cause: Oracle Web Cache has received a response that contains a malformed Oracle-WebCache-OSSO response header. It is possible that this Oracle Web Cache release is incompatible with the origin server.
Action: Ensure that the Oracle Web Cache version is compatible with that of the origin server

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11942: CRL is enabled without enabling client side certificate.
Cause: CRL is enabled on one of the listening endpoints, without requiring client side certificate.
Action: Ensure that client side certificate is required on the endpoint.

Level: 1

Type: ERROR

Impact: Security

WXE-11950: Internal XML parser error. Error code: %d. Error Message: %s
Cause: An internal error occurred while inside the XML parser. Oracle 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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11951: invalid value for ESI redirect attribute
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11952: Start processing ESI document %.*s%.*s, nesting level %d
Cause: Start processing of an ESI document (template or fragment).
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11953: In ESI template %.*s%.*s, the fragment's site name and URL has been discovered as %.*s and %.*s
Cause: Start processing of an ESI fragment.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11960: Oracle Web Cache is unable to decode the URI passed in: %s
Cause: URI decoding was unsuccessful, and it will be used as it is.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11962: Oracle Web Cache is unable to allocate enough memory to parse ESI vars tag string
Cause: There was not sufficient memory for Oracle Web Cache to parse the string in the ESI vars tag.
Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11963: Oracle Web Cache failed to create new ESI fragment request. Template uri: %.*s
Cause: ESI fragment request could not be generated. This error is generally a result of insufficient memory.
Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11964: empty variable key in ESI vars tag
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11965: invalid variable name in ESI vars tag
Cause: The variable name specified in the ESI template by the ESI vars tag is not defined.
Action: See the Oracle Web Cache Administrator's Guide for valid ESI variable names.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11966: In %.*s%.*s, request header failed to be added to the include request.
Cause: There was not sufficient memory for Oracle Web Cache to include the request, or there was a request header parsing error.
Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11967: malformed request header when fetching %.*s%.*s.
Cause: This request header did not have a colon (:)and was malformed.
Action: If the problem persists, contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11968: ESI fragment request URI parsing error
Cause: There was an unexpected condition in parsing the URI in an ESI fragment.
Action: If the problem persists, contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11969: invalid ESI variable string type
Cause: Oracle Web Cache reached some invalid vars string type other than TEXT, VARIABLE, and CRLF.
Action: If the problem persists, contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11970: Cache key composition failed
Cause: Oracle Web Cache could not generate a cache key for an ESI fragment
Action: If the problem persists, contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11971: Oracle Web Cache attempted to return the $(QUERY_STRING) decoded
Cause: A $(QUERY_STRING) was requested to be returned in decoded format. $(QUERY_STRING) must be returned in encoded format.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-11972: Template host header does not match UMD host header for Portal UMD request. template header: %.*s UMD header: %.*s
Cause: In an Oracle Portal environment, a UMD specification is most likely using an incorrect URL specification. This could cause errors to be reported in the browser.
Action: Contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-11973: Site name cannot be resolved.
Cause: Requested site in ESI fragment request could not be resolved.
Action: Make sure that site name in the ESI request is correct.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11974: Incomplete URI for ESI fragment.
Cause: URI for ESI fragment only had "http://" and was considered incomplete.
Action: Make sure that the URL in the ESI request is complete.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11975: Corrupted login data in ESI environment metadata block.
Cause: The application delivered data that could not be parsed to Oracle Web Cache.
Action: Fix the application.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11976: Duplicate name %s in ESI environment metadata block.
Cause: The environment block contained multiple name entries.
Action: Remove the duplicate entries. Only the first entry is used.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-11977: Memory allocation failure while initializing login metadata hash table.
Cause: The Oracle Web Cache memory manager could not allocate any more memory.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11978: In ESI template %s%s, failed to add request header value.
Cause: Wrong request-header was specified.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the ESI template file and correct the error in request_header attribute.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11979: In ESI template %s%s, failed to add the request header because value is missing
Cause: Value field in the request-header was missing.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the ESI template file and correct the error in the request_header attribute

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-11985: Oracle Web Cache is unable to obtain the size of the default ESI fragment page %s.
Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows.
Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows, and then configure it in the Error Page of Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11986: The default ESI fragment page %s is too large.
Cause: The default ESI fragment was too large.
Action: Alter the size of the default ESI fragment to less than 32 KB.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11987: Oracle Web Cache fails to open the default ESI fragment page %s.
Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows.
Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows, and then configure it in the Error Page of Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11989: read error while loading default ESI fragment page %s
Cause: The default ESI fragment was not readable or did not exist in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows.
Action: Create a readable default ESI fragment in the $ORACLE_HOME/webcache/files on UNIX or ORACLE_HOME\\webcache\\files directory on Windows, and then configure it in the Error Page of Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-11997: ESI stack overflow
Cause: Current stack maximum depth was set too low.
Action: Contact Oracle Support about how to increase the maximum stack depth.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12001: ESI <esi:include> tag nesting in template %.*s%.*s is too deep.
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12002: Origin server busy exception in ESI template %.*s%.*s, fragment %.*s%.*s
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 Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12003: No connection exception in ESI template %.*s%.*s, fragment %.*s%.*s
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 Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12004: Network timeout exception in ESI template %.*s%.*s, fragment %.*s%.*s
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 Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Network

WXE-12005: HTTP Client Error 4xx exception in ESI template %.*s%.*s, fragment %.*s%.*s
Cause: The origin server returned an HTTP 4xx status code.
Action: Check for errors in the ESI template and fragment files.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12006: HTTP Server Error 5xx exception in ESI template %.*s%.*s, fragment %.*s%.*s
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12007: Incompatible fragment version exception in ESI template %.*s%.*s, fragment %.*s%.*s
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12008: Incorrect response header exception in ESI template %.*s%.*s, fragment %.*s%.*s
Cause: The response header of the ESI fragment caused an error.
Action: Correct the error in the ESI fragment.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12009: Incorrect ESI fragment exception in ESI template %.*s%.*s, fragment %.*s%.*s
Cause: Oracle Web Cache was unable to parse the ESI fragment.
Action: Correct the error in the ESI fragment.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12010: Incorrect XML Fragment exception in ESI template %.*s%.*s, fragment %.*s%.*s
Cause: Oracle Web Cache was unable to parse the XML fragment.
Action: Correct the error in the XML fragment.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12011: Generic exception in ESI template %.*s%.*s, fragment %.*s%.*s
Cause: A generic ESI exception occurred.
Action: Check the template and fragment, and then correct the error.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12012: No exception handler is defined in template %.*s%.*s:.
Cause: An uncaught ESI exception was detected. An error page is returned.
Action: Correct the syntax error in the ESI template.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12013: No resolved virtual host mapping was found for template.
Cause: A ESI template contained an unresolved virtual host mapping.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12014: The cached ESI inline fragment is stale because the origin server was contacted for a fresh copy of the parent page which contains this ESI inline fragment.
Cause: Because the cached object is stale, Oracle Web Cache will use the new fresh copy of the inline fragment.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12015: Non-fetchable inline fragment %.*s%.*s not found in cache or already expired, fetching template %.*s%.*s from origin server again.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12081: ESI parsing error. Dumping ESI content:
Cause: ESI parsing error.
Action: For any syntax errors, correct the ESI syntax. For any non-syntax related error, contact Oracle Support Services.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12082: Oracle Web Cache cannot parse ESI due to insufficient memory
Cause: Oracle Web Cache ran out of memory while parsing ESI.
Action: Adjust the maximum cache size in the Resource Limits page of Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12083: ESI parser internal error at line %d: %s
Cause: An ESI tag closed too early or there was an internal error of the ESI parser.
Action: For any syntax errors, correct the ESI syntax. For any non-syntax related error, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12084: JESI fragment preprocessing error
Cause: Preprocessing of JESI fragment failed.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-12085: ESI syntax error. Bad exception type at line %d.
Cause: An invalid token was encountered.
Action: Correct the error at the specified location in the ESI template.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12086: ESI syntax error. Unrecognized keyword %s is at line %d.
Cause: An invalid token was encountered.
Action: Correct the error at the specified location in the ESI template.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12087: Bad Location response header in ESI fragment response
Cause: A redirection response contained an invalid Location header.
Action: Make sure that the application Web server sends a valid Location header.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12088: ESI syntax error. The src attribute is missing at line %d.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12089: Syntax error. The name attribute is missing at line %d.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12090: ESI syntax error. Bad attribute value appears at line %d.
Cause: An invalid or empty value string was found.
Action: Correct the error at the specified location in the ESI template.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12091: ESI syntax error. Multiple ESI <esi:environment> tags appear in a single template at line %d
Cause: Multiple <esi:environment> tags in a single ESI template are not allowed.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Configure the ESI template with one <esi:environment> tag.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12092: ESI Syntax error. Multiple request_body elements appear at line %d.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12093: ESI syntax error. The max-age attribute is incorrectly formatted at line %d.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12094: ESI syntax error. String length exceeds maximum at line %d.
Cause: The string length exceeded the maximum limit.
Action: Contact Oracle Support to change the string length limit.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12095: ESI syntax error. A variable requires a key at line %d.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12096: ESI syntax error. The POST request method requires an request_body at line %d.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

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

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12098: ESI syntax error. The value of the fetchable attribute at line %d is invalid.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12099: ESI syntax error. The same attribute appears multiple times in an ESI element at line %d.
Cause: An attribute can appear only once within an ESI element.
Action: Correct the error at the specified location in ESI object.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12100: Exhausted process memory. Exiting process.
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 Oracle Web Cache process, if possible.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-12101: Maximum receive buffer size 2 MB reached.
Cause: Receive buffer size is bigger than 2 MB on Windows platforms.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Reduce receive buffer size to below 2 MB.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12102: Unable to locate memory block (%db). Oracle Web Cache extends cache size over maximum limit to %dMB.
Cause: Memory request was not fulfilled with existing process memory, even after forced garbage collection.
Action: 1. From http://web_cache_hostname:web_cache_stats_port, select review the Detailed Memory Statistics. If requesting block size for garbage collection is larger than object buffer size, then consider: a. Increase the object buffer size. Contact Oracle Support for further information. b. Increase the maximum cache size in the Resource page of Fusion Middleware Control. 2. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-12103: Unable to locate large memory block (%db). Oracle Web Cache extends cache size over maximum limit to %dMB.
Cause: Large block memory request was not satisfied with existing process memory, even after forced garbage collection.
Action: 1. From http://web_cache_hostname:web_cache_stats_port, select review the Detailed Memory Statistics. If requesting block size for garbage collection is larger than object buffer size, then consider: a. Increase the object buffer size. Contact Oracle Support for further information. b. Increase the maximum cache size in the Resource Limits page of Fusion Middleware Control.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-12104: Oracle Web Cache process has page faulted
Cause: The Oracle Web Cache process has caused a hard operating system memory page fault to occur. This may indicate the physical system is overloaded or there is insufficient physical memory for the specified cache size.
Action: Try decreasing the maximum cache size.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12200: Cache memory allocation for the cluster configuration block failed.
Cause: Memory allocation failed.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12201: Cache memory allocation for the cluster member table failed.
Cause: Memory allocation failed.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12202: Cluster member DNS lookup problem
Cause: Could not resolve the IP address from the cluster member's host name.
Action: Check the Cluster Members and Properties page of Fusion Middleware Control to see if the host name is correctly listed.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12203: Cluster member number %s owner slot allocation %s:%s
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12204: Add cluster member number %s
Cause: Normal notification behavior.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12205: Remove cluster member number %s
Cause: Normal notification behavior.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12206: Cluster member number %s already marked alive
Cause: The local cache tried to add the specified cluster member, but it was already marked as alive.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12207: Cluster member number %s already marked dead
Cause: The local cache tried to remove the specified cluster member, but it was already marked as dead.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12209: A %s node cluster successfully initialized
Cause: Normal notification behavior.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12212: Cluster member %s - %s configuration is invalid.
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12213: Cluster member %s - %s configuration is valid.
Cause: Normal notification behavior.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12217: Cluster member count %s is larger than maximum allowed %s
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 Fusion Middleware Control.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12400: HTTP request-header exceeds configured maximum individual header size ( %s ). Client IP: %s
Cause: Oracle 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 Fusion Middleware Control.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12401: HTTP request-header exceeds configured maximum combined header size. Client IP: %s
Cause: Oracle 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 Fusion Middleware Control.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12402: HTTP response-header parsing error: %.*s.
Cause: An HTTP response from the origin server contained a header or an individual header value that was malformed or unexpected.
Action: If the behavior is still as expected, no action is required. If the behavior is not as expected, check the application code which generates the specified header.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12403: HTTP response-header parsing error: %s ( %s ).
Cause: An HTTP response from the origin server contained a malformed header or an individual header value that was malformed or unexpected.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12404: The number of search keys exceeds the maximum limit of search keys in the Surrogate-Key response-header.
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12405: Illegal time format in HTTP response-header.
Cause: HTTP response-header contains an illegal time format.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12408: Unexpectedly large HTTP response-header.
Cause: An unexpectedly large response-header was received from the origin server, indicating a possible performance problem.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12409: Timeout while reading HTTP response.
Cause: No timely response received from the origin server, indicating that the origin server is down.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Start origin server, if it is not running.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12410: Error while reading HTTP response ( SSL error %d ).
Cause: Oracle Web Cache encountered an SSL read error.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12411: Non-parseable HTTP request-header line - questionable token syntax. Client IP: %s
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12412: HTTP request-header parsing error - malformed request line. Client IP: %s
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12413: Unable to get Oracle name of ESI template character set ( %.*s ).
Cause: A recoverable internal error occurred while doing character set conversion.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12414: Unable to get Oracle name of ESI fragment character set ( %.*s ).
Cause: A recoverable internal error occurred while doing character set conversion.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12415: Unable to do character set conversion.
Cause: Internal error. A system/library call has unexpectedly failed.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12416: NLS library failure while doing character set conversion.
Cause: Internal error. A system/library call has unexpectedly failed.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12417: HTTP request-header parsing error - no header name. Client IP: %s
Cause: An HTTP request from a browser contained a malformed header line; the header name delimiting colon (':') was not present.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12419: Dump of offending HTTP request-header line:
Cause: Any of the causes associated with errors 12411, 12412 and 12417.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-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.
Cause: The number of search keys in the Surrogate-Key response-header exceeded the allowed hard maximum of 200.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Revise the Surrogate-Key response-header with 200 or fewer search keys.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12421: HTTP request is invalid due to a duplicate header occurrence: \"%.*s\". Client IP: %s
Cause: An HTTP request from a browser contained multiple occurrences of the same header type.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12422: Duplicate header occurrence(\"%.*s\") is in HTTP request.
Cause: An HTTP request from a browser contained multiple occurrences of the same header type.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12423: Response ETag header has no value possibly indicating an application server problem. This message is only printed once per cache process.
Cause: The response contains a NULL or empty string ETag header. This could be a problem with the application server
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12424: Ignoring unrecognized token \"%.*s\" in Oracle-WebCache-OSSO response header.
Cause: Oracle Web Cache has received a response from origin server that contains a token in Oracle-WebCache-OSSO header that is not recognized by Oracle Web Cache.
Action: Ensure that the Oracle Web Cache version is compatible with that of the origin server

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12425: Malformed invalidation capability request header (\"%.*s\") in HTTP request.
Cause: An HTTP request from a browser contained a malformed invalidation capability request header.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-12700: Site %.*s did not match any defined sites, resulting in no End User Performance Monitoring for URI
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12701: Site %.*s matched one of the defined sites for which End User Performance Monitoring is ON.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12702: Site %.*s matched a defined site with End User Performance Monitoring OFF, resulting in no End User Performance Monitoring for URI
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12703: No matching End User Performance Monitoring rule found for site %.*s, resulting in End User Performance Monitoring for URI.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12704: There are no End User Performance Monitoring rules defined for site %.*s, resulting in End User Performance Monitoring for URI.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12705: Matching End User Performance Monitoring REGEXP rule found regexp:%s and the rule is %s
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.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12706: Matching End User Performance Monitoring SUBSTRING rule found. substring:%s and the rule is %s
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: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12712: OEMPERFFILE can only be set to an .html file.
Cause: The file specified by OEMPERFFILE must be an .html file, but it was not.
Action: Contact Oracle Support for help in specifying the correct OEMPERFFILE.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12713: OEMPERFFILE cannot be parsed. Use the following format: <SCRIPT SRC=\"%schronos_JavaScript_filename\"></SCRIPT> and restart Oracle Web Cache.
Cause: OEMPERFFILE could not be parsed.
Action: Use the following format for the value of OEMPERFFILE: <SCRIPT SRC=\"%schronos_JavaScript_filename\"></SCRIPT>. Then, restart Oracle Web Cache.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12714: Invalid string specified for OEMPERFFILE.
Cause: The file name specified by OEMPERFFILE is an invalid string.
Action: Contact Oracle Support for help in specifying the correct OEMPERFFILE.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12715: OEMPERFFILE contains an invalid path separator.
Cause: The file name specified for OEMPERFFILE contains an invalid path separator.
Action: Correct the file name specified for OEMPERFFILE.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12716: End-User Performance Monitoring is enabled.
Cause: Normal notification behavior. End-User Performance Monitoring is enabled. The event is written to the log file.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-12800: Oracle Web Cache fails to read the configuration file. Dynamic changes have not been applied.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Configuration

WXE-12801: Dynamic Changes Applied Successfully
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Configuration

WXE-12802: The cache server cannot dynamically mark the origin servers as running because they are not responding. Other selected dynamic changes are applied.
Cause: The origin servers were not responding. The cache server disregarded this dynamic change, but applied other dynamic changes.
Action: No action required.

Level: 1

Type: TRACE

Impact: Configuration

WXE-12803: Dynamic Changes Not Applied
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Configuration

WXE-12804: Event Log rolled over.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Logging

WXE-12805: Access log %s rolls over.
Cause: Access log rolled over as a result of an on-demand rollover request.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12806: Non-existent access log %s specified in rollover request.
Cause: On-demand rollover request was submitted with an invalid access log name.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12807: Event log not rolled over because the rollover file already exists.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Logging

WXE-12808: Access Log %s not rolled over because the rollover file already exists.
Cause: Access Log is rolled over as a result of on-demand rollover request.
Action: Submit another rollover request after more than one minute.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12809: Could not find the matching Origin Server entry in original configuration which the cache server is running with.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12810: ESI fragment log for access log %s is not rolled over.
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.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12811: Dynamic event log rollover fails because the event log file does not exist.
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.

Level: 1

Type: ERROR

Impact: Logging

WXE-12812: Dynamic event log rollover fails because the event log file could not be renamed.
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.

Level: 1

Type: ERROR

Impact: Logging

WXE-12813: Access log name is not specified in rollover request.
Cause: On-demand access log rollover request did not contain the access log name.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12814: ***** Request message notification begin *****
Cause: Request-specific event_log messages.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12815: ***** Request message notification complete *****
Cause: Request-specific event_log messages.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12817: Directory %s size reduced from %dMB to rollover criteria %dMB
Cause: The specified logfile was automatically purged because the directory exceeded the maximum size threshold designated in the configuration.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12818: Logfile %s (size %dMB) deleted due to rollover criteria (%dMB)
Cause: The specified logfile was automatically purged because the directory exceeded the maximum size threshold designated in the configuration.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12819: event_log reverted to old-style logging with WCDEBUG enabled
Cause: When the event_log is configured using the MODE="NEW" attribute (the default configuration), but the WCDEBUG feature is enabled, the logging sub-system must revert to the MODE="OLD" configuration.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12820: Logfile %s (size %dMB) deleted due to time-based retention criteria
Cause: The specified logfile was automatically purged because the directory exceeded the maximum retention period designated in the configuration.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Logging

WXE-12822: Oracle Web Cache fails to rename file from %.*s to %.*s (%s)
Cause: Dynamic event log rollover failed because Oracle Web Cache could not rename the file.
Action: Check the permissions of the event log file and if another application is using the event log file.

Level: 1

Type: TRACE

Impact: Logging

WXE-12900: Oracle Web Cache fails to read the final byte ('X') from Oracle Web Conferencing client; redirect fails.
Cause: Oracle Web Conferencing client did not send the character X to mark request end
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12901: Oracle Web Cache fails to send the message to the Oracle Web Conferencing client; redirect fails.
Cause: Oracle Web Cache could not send Oracle Web Conferencing protocol message to client.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12902: The mx list is empty in the Oracle Web Conferencing path %s.
Cause: The configured mx path set was incorrect.
Action: Configure the correct mx path.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-12903: The Oracle Web Conferencing pass descriptor fails; Error: %s.
Cause: Oracle Web Cache was unable to pass descriptor to the mx server.
Action: Check the mx server configuration and log files.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12904: Oracle Web Conferencing redirect did not occur for mx path = %s.
Cause: Oracle 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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12905: Oracle Web Conferencing redirect is successful.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-12906: The Windows socket could not be set to blocking; Error: %s.
Cause: The error was caused the by the error printed in the message.
Action: Debug from the error printed in the message.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12907: The Oracle Web Conferencing URL is not valid.
Cause: The URL received by webcache is invalid.
Action: Check the Oracle Web Conferencing configuration.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-12908: The Oracle Web Conferencing pass descriptor is successful.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13001: Virtual Host Map %s has a mixture of HTTP and HTTPS Protocol origin servers. All origin servers for a virtual host map must use the same protocol.
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 Fusion Middleware Control, correct the mapping. Then, restart Oracle Web Cache.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13002: Maximum allowed incoming connections are %u
Cause: Normal notification behavior indicating the maximum number of concurrent connections which will be accepted.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WXE-13003: Configuration error. Stopping admin or cache server.
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.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13005: The session definition for the session \"%s\" is missing but used in the WTI session key configuration for server \"%s\".
Cause: A non-existent session definition is referenced by its name in WTI session key configuration in the configuration file.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Modify the configuration to either add the session definition or used another existing definition.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13006: The session inactivity timeout for the session \"%s\" is missing but required in the WTI session key configuration for server \"%s\".
Cause: The session used for WTI session key does not have an inactivity timeout defined.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. A WTI session key is used for security purposes. It is based on a user session which should have an inactivity timeout. Please add the inactivity timeout to the session definition for this session.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13007: The specified listening IP address \"%s\" is not valid.
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 * 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.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13008: CRL is enabled for listen port %s but no CRL file or path is specified.
Cause: Both port specific and global settings of SSLCRLPATH and SSLCRLFILE are NIL but SSLCRLENABLE is set to "YES
Action: Modify the configuration to either specify a valid SSLCRLPATH and SSLCRLFILE or disable CRL checking.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13009: CRL is enabled for listen port %s without enabling client side certificate.
Cause: CLIENT_CERT must be set to "YES" or "OPTIONAL" when SSLCRLENABLE is set to "YES".
Action: Modify the configuration and correct CLIENT_CERT setting or disable CRL checking.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13010: MAXLOGSIZE (%d) cannot be larger than MAXREPSIZE (%d)
Cause: The maximum logfile rollover size specified by the MAXLOGSIZE parameter is larger than the repository rollover size specified by the MAXREPSIZE configuration parameter.
Action: Reduce the size specified by the MAXLOGSIZE configuration parameter, or increase the size specified by the MAXREPSIZE parameter.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13011: Invalid tweak parameter \"%s\" value \"%s\"
Cause: The specified tweak parameter contains an unknown or invalid value.
Action: Check the documentation for the set of valid values for the specified tweak parameter.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13050: Multiple access logs use the same file name: %s
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.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13051: List of IP addresses only valid for ALLOW=\"LIST_OF_IPS\" option
Cause: The specified secure subnet IP address(es) can only be supplied when the ALLOW="LIST_OF_IPS" attribute is specified for the SECURESUBNET element.
Action: Remove the list of IP addresses, or change the ALLOW attribute to the value "LIST_OF_IPS".

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13052: Cache attribute INSTANCENAME %s does not match environment variable INSTANCE_NAME %s.
Cause: The instance name specified in configuration file is wrong.
Action: This does not affect Web Cache from starting up since runtime Web Cache do not make use of this attribute. This attribute is used by the Enterprise Manager to find the correct CACHE element.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13074: A session caching rule refers to an invalid session name: %s
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 Fusion Middleware Control.
Action: Edit webcache.xml and set the session ID to a valid session definition.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13075: A session binding rule refers to an invalid session name: %s
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 Fusion Middleware Control.
Action: Edit webcache.xml and correct the session definition for the specified session ID.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13076: A caching rule refers to an invalid expiration rule: %s
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 Fusion Middleware Control.
Action: Edit webcache.xml and find the specified expiration rule and replace it with a valid expiration rule.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13077: A caching rule refers to an invalid multi-version cookie rule: %s
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 Fusion Middleware Control.
Action: Edit webcache.xml and find the multi-version cookie rule listed in the error message. Replace the rule with a valid one.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13078: A caching rule refers to an invalid session rule: %s
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 Fusion Middleware Control.
Action: Edit webcache.xml and find the specified session rule. Replace the rule with a valid one.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13079: Oracle Web Cache did not find a matching CACHE element in webcache.xml for the current host name (%s) and Oracle home (%s).
Cause: Oracle Web Cache was unable to find a CACHE element for this cache.The configuration file may be in error.
Action: Contact Oracle Support to fix the configuration file.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13080: No NAME attribute is specified in ROLLOVER element under ACCESSLOGSTYLES
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.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13081: Any Set-Cookie is not configured with the a session binding mechanism other than Cookie-based.
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.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13082: Duplicate CACHE element found in webcache.xml for current instance name (%s), component name (%s), hostname (%s) and ORACLE_HOME (%s)
Cause: Identified a duplicate 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.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13106: Log file rollover schedule refers to an invalid TIME value for the HOURLY frequency: %u
Cause: Time value specified for the HOURLY frequency was invalid.
Action: TIME must be set to a nonzero positive integer value less than 60.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13107: Log file rollover schedule refers to an invalid TIME value for the DAILY frequency: %u
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.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13108: Log file rollover schedule refers to an invalid TIME value for the WEEKLY frequency: %u
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.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13109: XML parsing error in %s. Error code %u: %s
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.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13110: XML parser initialization error. Error code: %u
Cause: Unable to initialize the XML parser.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13111: XML parsing failed for file: %s. Error Code: %u
Cause: An XML parsing error occurred when parsing the specified file.
Action: Review associated error messages for more information about the problem.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13112: XML parsing failed. Error Code: %u
Cause: Failed to parse an XML message.
Action: Review associated error messages for more information about the problem.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13113: Syntax error in %s. Exception: \"%s\" in attribute \"%s\" having value \"%s\" in element %s
Cause: An exception occurred while parsing the specified file.
Action: Edit the specified file to make it a valid XML object.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13114: A root directory mapping must be specified before all other mappings
Cause: This error may have occurred if the internal configuration has been changed.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13115: Out of memory error while scanning object root
Cause: The process ran out of memory while scanning for objects in the object root.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Memory

WXE-13116: An error occurred scanning the directory %s
Cause: Oracle Web Cache was unable to get the contents of the specified directory.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13117: Failed to add MIME type extension to pool: %s
Cause: An error occurred while processing the MIME type extensions settings.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13118: Out of memory error while initializing MIME type information
Cause: An error occurred while processing the MIME type extensions settings.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Memory

WXE-13119: Duplicate origin server hosts specified for host %s port %s.
Cause: There are duplicate entries in the HOST section of the webcache.xml file.
Action: Remove the duplicate entries from webcache.xml.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13120: CACHEWITH and CACHEWITHOUT cannot both have the value \"NO\" in a session caching policy for session %s.
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.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13121: The caching rule for %s contains more than one multi-version cookie policy based on the same cookie: %s.
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.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13122: The caching rule for %s contains more than one session-caching policy based on the same session: %s.
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.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13123: Site name %s:%s%s exceeds maximum individual header limit.
Cause: The site name was set to more than the maximum single header limit as defined in the security section.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Increase the maximum individual header size limit in the Security page of Fusion Middleware Control, so that the site name and port number string together is less than the specified limit.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13124: Alias name %s:%s%s exceeds maximum individual header limit %d.
Cause: The alias name was set to more than maximum individual header limit as defined in the security section.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Increase the maximum individual header size limit in the Security page of Fusion Middleware Control or change the alias name in the Sites page of Fusion Middleware Control, so that the alias name and port number string together is less than the specified limit.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13125: internal.xml does not have CALYPSOINTERNALPARAMS element.
Cause: Unable to find CALYPSOINTERNALPARAMS element in internal.xml.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check whether internal.xml conforms to internal.dtd.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13127: Oracle XML Schema processor failed to initialize%s.
Cause: Oracle XML Schema Processor failed to initialize.
Action: If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13128: XML file%s did not pass validation against schema checking%s.
Cause: Error occurs in validating the XML file against its corresponding XML schema
Action: Fix the error accordingly in the XML file

Level: 16

Type: ERROR

Impact: Configuration

WXE-13129: Setting internal tweak parameter '%s' value to '%s'.
Cause: Tweak mechanism was used to change the specified internal tweak parameter to the stated new value. This occurs only at startup.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Configuration

WXE-13130: Ignoring internal tweak parameter '%s'; value '%s' is illegal
Cause: Tweak mechanism can be used to change the specified internal tweak parameter's value, but only if the value is legal for that parameter. This occurs only at startup.
Action: Specify a legal value (please contact Oracle Support) and try again.

Level: 1

Type: WARNING

Impact: Configuration

WXE-13131: Ignoring unknown internal tweak parameter '%s'.
Cause: An attempt was made to use the tweak mechanism for an unknown internal tweak parameter. Because the parameter name was unknown, its value was ignored.
Action: Fix the name to be a legitimate internal tweak parameter (please contact Oracle Support) and try again.

Level: 1

Type: WARNING

Impact: Configuration

WXE-13132: Invalid logfile retention specified: %d %s
Cause: The specified logfile retention period is invalid. This problem can occur is the frequency definition is incorrectly spelled.
Action: Verify that the retention period count and frequency are correct.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13133: Host 'name' is required
Cause: The 'name' attribute of the 'host' element was not specified, or was specified as an empty value.
Action: Specify a unique host name.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13134: Oracle Web Cache did not find a matching CACHE element in webcache.xml for the current host name (%s), Oracle instance (%s) and system component name (%s).
Cause: Oracle Web Cache was unable to find a CACHE element for this cache.The configuration file may be in error.
Action: Contact Oracle Support to fix the configuration file.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13200: Access logging was skipped as the request had not been parsed properly.
Cause: Due to an error in request parsing, access logging could not be completed.
Action: No action required.

Level: 16

Type: ERROR

Impact: Configuration

WXE-13212: Access log file %s could not be opened.
Cause: Access log file could not be opened.
Action: Check the status of access log file. For example, check the permission of the file.

Level: 1

Type: ERROR

Impact: Logging

WXE-13213: Invalid access log field name: %s
Cause: An invalid access log field is specified in the configuration file webcache.xml.
Action: Set valid access log field name.

Level: 1

Type: ERROR

Impact: Logging

WXE-13215: I/O Error when writing access Log buffer to file. error number: %d
Cause: I/O error happened when Oracle 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.

Level: 1

Type: ERROR

Impact: Logging

WXE-13250: Search key configuration error
Cause: Invalid Oracle Web Cache configuration for search key.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Configuration

WXE-13251: The HTML file for End-User Monitoring was not found
Cause: End-User Monitoring configuration error.
Action: Disable End-User Monitoring or restore the HTML file that is missing. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13252: On Demand Log File Rollover for file %s was not successful. File %s could not be created.
Cause: The rollover file could not be created.
Action: Check the file permissions.

Level: 1

Type: WARNING

Impact: Logging

WXE-13301: A failure occurred with DNS lookups. No more DNS lookups will occur.
Cause: The DNS server might be unavailable.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the DNS configuration on the local machine.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13302: Failed to open directory: %s
Cause: Directory could not be opened because it does not exist or the access permissions are incorrect.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Check the configuration and the permissions for accessing the directory.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13305: Failed to assign port %s: %s
Cause: The selected port is being used by another application.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Change the port to an unused port.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13306: Failed to configure resources for port %s: %s
Cause: System listen function call failed.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Restart Oracle Web Cache. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13307: Failed to allocate resources for port %s: %s
Cause: Socket creation failed.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. If the problem persists, Restart Oracle Web Cache and check open file descriptors.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13308: Failed to listen on port %s: %s
Cause: Generally occurs when the port is in use by another application.
Action: Change the port to an unused port. Restart Oracle Web Cache. If the problem persists, contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13309: Listening on port %s
Cause: Generally occurs when the port is in use by another application.
Action: Change the port to an unused port. Restart Oracle Web Cache. If the problem persists, contact Oracle Support.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-13310: Problem opening file %s (Access Denied).
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13312: Problem creating file %s (File Already Exists).
Cause: The file could not be created because it already exists.
Action: Choose a file name that does not exist.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13313: Problem opening file %s (Invalid Drive).
Cause: The file could not be opened because the drive name is invalid.
Action: Correct the file specification.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13314: Problem opening file %s (Invalid Name).
Cause: The file could not be opened because the file name is invalid.
Action: Correct the file specification.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13315: Problem opening file %s (Too Many Open Files).
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 Oracle Web Cache.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13316: Problem opening file %s (File Not Found).
Cause: The file could not be opened because the file could not be found.
Action: Correct the file specification.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13317: Problem opening file %s (Sharing violation).
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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13318: Problem opening file %s (Is a directory).
Cause: The file could not be opened because it is directory.
Action: Correct the file specification.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13319: Problem opening file %s, system error %s (Internal error).
Cause: There was been an unknown error opening the file.
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-13350: Error during network receive, system error %s
Cause: There was system error during the networking receive.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13351: Timeout during network receive, socket number %s
Cause: There was timeout during the networking receive.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13365: Error during network send, system error %s
Cause: There was system error during the networking send.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13366: Timeout during network send, socket number %s
Cause: There was timeout during the networking send.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13380: Error during SSL handshake, system error %s
Cause: There was system error during the SSL handshake.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13381: Timeout during SSL handshake, socket number %s
Cause: There was timeout during the SSL handshake.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13382: File %s cannot be opened.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13383: Unable to initialize DNS lookups
Cause: Cannot use DNS for TCP/IP host resolution.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13400: parsing error of <!-- WEBCACHETAG--> and <!-- WEBCACHEEND--> at offset %d
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13500: Login Information missing for WTI key server \"%s\"
Cause: A key server with the given server name is defined but no login (username, password) information is provided.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please reconfigure WTI key server section to add the login information for this key server or remove this key server.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13502: WTI Processor HTML parsing failure.
Cause: A failure is reported by the HTML parser.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Validate this HTML page's syntax.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13503: WTI HTML parser context creation failure.
Cause: The system may be running low in memory.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please increase the system memory.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13504: WTI form descriptor creation failure.
Cause: The system may be running low in memory.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please increase the system memory.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13505: WTI processor failed in memory allocation.
Cause: The system may be running low in memory.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please increase the system memory.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13508: The WTI processor failed to generate a form descriptor.
Cause: A form descriptor cannot be generated in WTI processor.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please check other form description generation error messages for detail.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13509: The WTI processor failed to get a WTI session key.
Cause: A WTI session key cannot be retrieved by the WTI processor.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Please check other messages to find out the specific reason for key retrieval failure.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13540: WTI processor found request invalid.Error Descriptor:%s
Cause: The cause should be shown by other more detailed messages.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13541: WTI processor: request MAC verification failed.
Cause: The cause should be shown by other more detailed messages.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13570: WTI processor found unexpected request parameter ordering.
Cause: The cause should be shown by other more detailed messages.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-13600: Assertion failed.
Cause: Assertion is failed. Diagnostic information is printed in trace dump file.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-13601: Signal SIGSEGV caught
Cause: Signal SIGSEGV is caught. Diagnostic information is printed in trace dump file.
Action: Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13602: Signal SIGBUS caught
Cause: Signal SIGBUS is caught. Diagnostic information is printed in trace dump file.
Action: Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13603: Signal SIGFPE caught
Cause: Signal SIGFPE is caught. Diagnostic information is printed in trace dump file.
Action: Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13604: Signal SIGSEGV caught
Cause: Signal SIGSEGV is caught. Diagnostic information is printed in trace dump file.
Action: Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13606: Signal SIGABRT caught
Cause: Signal SIGABRT is caught. Diagnostic information is printed in trace dump file.
Action: Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-13704: Compression error in: %s
Cause: A gzip library call failed.
Action: If the problem persists, contact Oracle Support.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-13705: Oracle Web Cache compresses object. Original size: %d bytes; Compressed size: %d bytes.
Cause: Normal trace behavior.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13708: Compression is not yielding any benefit.
Cause: Compression was not able to reduce the size of the object.
Action: Disable compression for this object..

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13709: Compression disabled for invalid MIME type '%.*s'; non-ascii or non-printable
Cause: An invalid MIME type was identified. The MIME type either contained non-ascii characters, or contained non-printable (undisplayable) characters. Compression is disabled for this MIME type.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13710: Compression disabled for invalid MIME type '%.*s'; too large
Cause: An invalid MIME type was identified. The MIME type was too large to be stored in the MIME type compression table. Compression is disabled for this MIME type.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13720: Oracle Web Cache disables compression for %s due to a low rate: %d%%.
Cause: Objects with this MIME type, file extension, or both, were compressed three times.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13722: Compression policy for %s has expired. Re-instrumenting.
Cause: Six hours have passed since the compression setting for this MIME type and file extension were set. As a result, the compression setting was reset.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13730: Object will be compressed.
Cause: No headers or policies disabled compression, so Oracle Web Cache compressed the object.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13731: Object is too small to warrant compression.
Cause: The requested object was too small to compress.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13732: Compression disabled for this object by a Surrogate-control header.
Cause: The Surrogate-Control header indicated that compression should be disabled.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13733: Compression disabled for this Site.
Cause: An application-specific caching specified that compression should be disabled.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13734: Compression disabled for this object by caching rule.
Cause: A caching rule specified that compression should be disabled.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13735: Compression is disabled because the browser has known issues.
Cause: The browser was either Netscape version 4 or less, or it was Internet Explorere version 5.5 or less. These browsers have known issues.
Action: Upgrade the browser.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13736: Compression is disabled because the browser does not support compression.
Cause: The user's browser does not support compression.
Action: Upgrade the browser.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13737: Compression is internally disabled for: %s.
Cause: Compression for this object's MIME type or file extension is internally disabled.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13738: Compression disabled because %s has a low compression rate.
Cause: The compression rate on this MIME type, file extension, or both, was poor. Therefore Oracle Web Cache is disabling compression for this type.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-13817: I/O Logging enabled; using file %s
Cause: As specified, I/O Logging has been enabled using the specified file.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-13818: I/O Logging disabled; file %s could not be accessed
Cause: As specified, I/O Logging has been enabled using the specified file.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-13916: Optimizer failure on pattern '%.*s' - trying original '%.*s'
Cause: The optimized regular expression failed to compile; an attempt was made to compile the original supplied (unoptimized) expression.
Action: No action required.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-14000: unknown internal error
Cause: error number is properly set
Action: check which module is not setting the error number

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14001: bad arguments
Cause: bad request
Action: check the code which is sending wrong argument to the calling function

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14002: Error while sending the request to origin server (id=%d) %s:%d
Cause: The request to the origin server failed.
Action: Ensure that the origin server is running.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14003: Error while receiving response from the origin server (id=%d) %s:%d
Cause: Oracle Web Cache was unable to receive a response from the origin server.
Action: Ensure that the origin server is running.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14004: HTTP status code error
Cause: The origin server returned a non-HTTP status code.
Action: Check the origin server to determine what application is sending the response.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14005: Content-Type buffer is too small
Cause: The buffer pool memory was not sufficient.
Action: Adjust the maximum individual header size limit in the Security page of Fusion Middleware Control. If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14006: SSL handshake with origin server (id=%d) %s:%d fails.
Cause: The SSL handshake between Oracle Web Cache and the origin server failed.
Action: Check certificate configuration on the origin server.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14007: Connect request terminates.
Cause: The connection request to the origin server was terminated.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14008: Create request fails.
Cause: Oracle Web Cache failed to create a request to the origin server.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14009: Header operation fails.
Cause: Oracle Web Cache could not write to the HTTP response header from the origin server. This occurs if the Oracle Web Cache computer is experiencing a system memory problem.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14010: Invalid authentication credentials for proxy server
Cause: The user name and password for the proxy server failed.
Action: Correct the user name and password in the Origin Servers page of Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14011: Proxy tunnel authentication required
Cause: The user name and password for the proxy server failed.
Action: Correct the user name and password in the Origin Servers page of Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14012: Bad response from proxy tunnel
Cause: The proxy tunnel response was incorrect.
Action: Check the proxy server configuration and setup.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14013: Send request to origin server (id=%d) %s:%d times out.
Cause: The request to the origin server exceeded the network timeout limit.
Action: If the problem persists, adjust the network timeout between Oracle Web Cache and the origin server in the Resource Limits page of Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14014: Receive request from origin server (id=%d) %s:%d timed out.
Cause: The response from the origin server exceeded the network timeout limit.
Action: If the problem persists, adjust the network timeout between Oracle Web Cache and the origin server in the Resource Limits page of Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14015: Browser terminates connection; the request to the origin server is terminated.
Cause: The browser terminated its connection. As a result, Oracle Web Cache terminated its connection to the origin server.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14016: Connection to origin server (id=%d) %s:%d fails.
Cause: The origin server is down.
Action: Check the origin server.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14017: Connection to origin server times out.
Cause: The connection to the origin server exceeded the network timeout limit.
Action: If the problem persists, adjust the network timeout between Oracle Web Cache and the origin server in the Resource Limits page of Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14018: Socket creation fails for origin server.
Cause: The Oracle Web Cache computer has run short of system resources.
Action: If the problem persists, increase the Maximum Incoming Connections setting in the Resource Limits page Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14019: Dynamic origin server DNS failure
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 Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14020: Origin server rejects queue entry.
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 Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14021: Capacity, as set by Web Cache, is exceeded for all origin servers that are available for processing this request.
Cause: Oracle 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 Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14022: Load balancing and failover functionality fails.
Cause: All of the origin servers were down. Oracle Web Cache will continue to poll the origin server until they are back online.
Action: Check the state of the origin servers.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14023: No origin server is running.
Cause: All communication to the origin servers has failed. Oracle Web Cache will continue to poll the origin server until they are back online.
Action: Check the state of the origin servers.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14024: Dynamic origin server is not allowed for request.
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 Fusion Middleware Control.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14025: Dynamic connection to origin server (id=%d) %s:%d fails.
Cause: Oracle 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.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14026: Out of memory
Cause: Oracle Web Cache is running out of memory.
Action: No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14027: Connection request to origin server (id=%d) %s:%d times out.
Cause: The connection between Oracle Web Cache and the origin server timed out.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14028: incomplete header
Cause: The HTTP response from the origin server did not contain a properly formatted HTTP header.
Action: Check the application sending the response.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14029: invalid header
Cause: The HTTP header response from the origin server contained an invalid field.
Action: Check the application sending the response.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14030: Single response header is too long.
Cause: Origin Server is sending longer header than Oracle Web Cache is expecting.
Action: No Action required

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14031: Total header length is too long
Cause: Origin Server is sending longer headers than Oracle Web Cache is expecting.
Action: Check the Origin Server setting.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14032: Buffer finished before \ is found.
Cause: The response from the origin server was not properly formatted.
Action: If the problem persists, check the application sending the response.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14033: Chunk length exceeded more 256 digits.
Cause: Origin Server is sending wrong chunking length header than specified in HTTP specification.
Action: Check the Origin Server setting.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14034: Network %.*s during origin server %.*s (details: internal=%.*s system=%.*s)
Cause: A network operation failure was encountered between the origin server and Oracle Web Cache, so the request could not be completed.
Action: Check network status on the Oracle Web Cache host machine.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14035: strtol utility returned an error.
Cause: Internal string function failed.
Action: No action required.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14036: time overflow
Cause: Invalid time string from Origin Server
Action: Check the Origin Server configuration setting

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14037: illegal time format
Cause: The creation time received from the origin server was for a time in the future.
Action: Check the application sending the response.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14038: invalidation operation
Cause: Internal error
Action: no action required

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14039: HTTP response not found
Cause: An HTTP response from the origin server was not found.
Action: Check the application sending the response.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14040: overflow
Cause: Could be wrong time format
Action: no action required

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses

WXE-14041: invalid format
Cause: The response contained an invalid time format or inversion of an integer.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14044: Unexpected EOF while reading HTTP response-header.
Cause: Connection prematurely closed by origin server.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14045: Error Parsing Chunk Length for %.*s%.*s.
Cause: Incorrect chunk length
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14047: Oracle Web Cache encounters an invalid HTTP response.
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.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14050: The request is granted with view permission for the cached object.
Cause: In response to a security validation request from WebCache on behalf of the request, the origin server responded with "304 Not Modified", with the Surrogate-Control: view-granted token. The cached object will be used to serve the request.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14051: The request is validated with cached version %.*s
Cause: In response to a version validation request from Oracle Web Cache on behalf of the request, the origin server responded with "304 Not Modified", specifying the cached version in the Surrogate-Control: version token to be served to the client.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14052: New content is received from the origin server in response to a validation request from WebCache.
Cause: In response to a security or version validation request from Oracle Web Cache on behalf of the request, the origin server responded with new content. The cached objects will be updated accordingly.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14056: Origin server error: empty version string in Surrogate-Control in the response.
Cause: The response contains an empty Surrogate-Control: version string This will be treated as an invalid response, and an error will be sent to the client.
Action: Check that the origin server has proper support for version validation based caching.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14059: Object validation aborted.
Cause: The response will not be used to update the validation-required entry in the cache because it was determined that it is not cacheable.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14060: The response contains Surrogate-Control: secure-view, indicating the object requires security validation for all cache hits.
Cause: The Surrogate-Control header contains a secure-view token indicating that the cached entry requires security validation for all hits.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14061: The response contains the Surrogate-Control: version token with value %.*s, indicating the object requires version validation for all cache hits.
Cause: The Surrogate-Control header contains a Surrogate-Control: version token indicating that the cached entry requires version validation for all hits.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14062: The validation-required cache entry is updated with new content for an existing version %.*s
Cause: The complete response for an existing version of the validation-required cache entry was successfully received and the version in the entry is updated with the new response.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14063: The validation-required cache entry is updated with content for a new version %.*s
Cause: The complete response for a new version of the validation-required object was successfully received and the cache entry is updated with the new response.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14064: Failed to insert the new version %.*s to the validation-required cache entry as the maximum allowed versions is reached for the entry, and none of the existing versions can be removed.
Cause: The cache entry already contains the maximum allowed number of version objects, and all of them are currently being updated, so the new version received can not be added to the entry.
Action: Adjust the maximum allowed version objects per cache entry if you prefer to have all versions cached.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14066: Origin server denied view permission for the request.
Cause: In response to a security validation request, or Oracle Single Sign-On authentication request from Oracle Web Cache on behalf of the request, the origin server responded with "401 Unauthorized", meaning the user does not have view permission for the requested object in cache.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14067: Origin server error: missing Surrogate-Control: view-granted token in the response for a security validation request from WebCache.
Cause: In response to a security validation request from Oracle Web Cache on behalf of the request, the origin server responded with "304 Not Modified", but without the Surrogate-Control: view-granted token required to indicate that an authorization check has been performed. This will be treated as an invalid response, and an error will be sent to the client.
Action: Check that the origin server has proper support for security validation based caching.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14068: Origin server error: incorrect Surrogate-Control: version string in the response for a version validation request from WebCache.
Cause: In response to a version validation request from Oracle Web Cache on behalf of the request, the origin server responded with "304 Not Modified", but without the Surrogate-Control: version token required to indicate that version check has been performed, or with an incorrect version token that does not match any versions specified in the request. This will be treated as an invalid response, and an error will be sent to the client.
Action: Check that the origin server has proper support for version validation based caching.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14070: Origin server error: unexpected 304 response.
Cause: In response to regular request from Oracle Web Cache with no validation clause, the origin server returned "304 Not Modified". This will be treated as an invalid response, and an error will be sent to the client.
Action: Check that the origin server has proper support for validation based caching.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14071: Unexpected EOF while reading HTTP response-body.
Cause: Connection prematurely closed by origin server.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14072: The Location header of the 302 response is not found or is empty.
Cause: The origin server response was a 302 redirect response, but the required Location header was not found or was empty.
Action: Check the application sending the response.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14130: [site #%.*s - %s][filter type: %s][rule #%.*s%s]%.*s[action: allow]
Cause: The request matched a request-filtering rule for a filter type and the action specified for a rule match was allow. Request was allowed for this filter type. The other filter types, if any, were checked.
Action: No action required, unless this action is not the desired behavior.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14131: [site #%.*s - %s][filter type: %s][rule #%.*s%s]%.*s[action: allow - MONITOR ONLY]
Cause: The request matched a request-filtering rule for a filter type and the action specified for a rule match was allow. However, the rule was set to be in monitor-only mode, so the statistics for the rule were updated, but otherwise the rule was treated as disabled. The other rules, if any, for this filter type were checked.
Action: No action required, unless this action is not the desired behavior. This message is for informational purposes.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14132: [site #%.*s - %s][filter type: %s][rule #%.*s%s]%.*s[action: deny - %s]
Cause: The request matched a request-filtering rule for a filter type and the action specified for a rule match was deny. The request was denied.
Action: No action required, unless this action is not the desired behavior.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14133: [site #%.*s - %s][filter type: %s][rule #%.*s%s]%.*s[action: deny - %s - MONITOR ONLY]
Cause: The request matched a request-filtering rule for a filter type and the action specified for a rule match was deny. But the rule is in monitor-only mode, so the statistics for the rule were updated, but otherwise the rule was treated as disabled. The other rules, if any, for this filter type were checked.
Action: No action required, unless this action is not the desired behavior. This message is for informational purposes.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14143: Request filtering needs to check the POST body, but the POST body size exceeds the configured maximum. Oracle Web Cache returns a bad request error response.
Cause: Oracle Web Cache received an HTTP request with a POST body which request filtering must check, but the POST body size exceeds the maximum configured POST ody size. Oracle Web Cache returns a bad request error response.
Action: If the problem persists and rejecting the request is not acceptable, increase the configuration setting for the maximum POST body size if request filtering is needed in the Oracle Web Cache configuration. You configure this setting in the Security page (Properties > Security) of Oracle Web Cache Manager.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14147: [site #%.*s - %s][filter type: %s][action: no match on any non-MONITOR-ONLY rule, so check other filters]
Cause: The request did not match any request-filtering rule for the Privileged IP filter type which is not a monitor-only rule. Therefore, check the other request filters for this request.
Action: No action required, unless this action is not the desired behavior. This message is for informational purposes.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14153: The request is from a Privileged IP address, so other request filter checks are bypassed.
Cause: The normal request filtering checks were bypassed for this request, because the request is coming from a privileged IP.
Action: No action required, unless this action is not the desired behavior.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-14200: One or more sites are ACL-protected. Initializing secure caching tables.
Cause: Normal notification. At least one site was configured as ACL-protected site. Oracle Web Cache will enable secure caching for those sites.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-14201: XML parser for WebDAV ACL initializes successfully.
Cause: Normal notification. XML parser for WebDAV ACL was initialized successfully.
Action: No action required.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

WXE-14210: Invalid authorization header (%s)
Cause: The authorization header in the request lacked the necessary items or was invalid.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14213: The requested object is ACL-protected. Starting ACL evaluation.
Cause: The client requested an object from an ACL-protected site. Therefore, an ACL evaluation was started.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14214: Oracle Web Cache does not have fresh copies of all ACLs. ACL evaluation terminates.
Cause: Required ACL object was missing, stale or in update status. Therefore, ACL evaluation was terminated.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14215: Oracle Web Cache does not have all the necessary information for the requesting user (%s). ACL evaluation terminates.
Cause: The user/group table did not contain an entry of the user or the user's group membership was not updated yet. Therefore, ACL evaluation was terminated.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14216: ACL evaluation completes. Access granted to the user (%s).
Cause: The user has read privilege for the requested URL.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14217: ACL evaluation completes. Access denied for the user (%s).
Cause: The user does not have read privilege for the requested URL.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14221: The response does not contain a valid X-Oracle-Current-User header.
Cause: The response does not contain the X-Oracle-Current-User header or the header is invalid.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14225: The insertion of user (%s) to the user/group table fails.
Cause: Oracle Web Cache tried to insert a user entry for the user but failed.
Action: No action required.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-14229: A user and a group have the same principal URL (%s).
Cause: A group had the same principal URL as a user.
Action: Check the origin server's user and group settings.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14233: Propfind request for fetching the password verifier of user (%s) is composed.
Cause: Propfind request for the password verifier of the requesting user was composed.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14234: Propfind request for fetching the group-membership of user (%s) is composed.
Cause: Propfind request for the group membership of the requesting user was composed.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14235: Propfind request for ACL HREF or ancestor ACL HREFs of the resource (%s) is composed.
Cause: Propfind request for ACL HREF, ancestor ACL HREFs, or both ACL HREF and ancestor HREFs was composed.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14236: Request for fetching ACL (%s) is composed.
Cause: Propfind request for fetching ACL object was composed.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14240: Starting post-processing of user password verifier.
Cause: Starting post-processing of password verifier.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14241: Starting post-processing of user groupmembership.
Cause: Starting post-processing of user groupmembership.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14242: Starting post-processing of resource ACL HREF.
Cause: Starting post-processing of resource ACL HREF.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14243: Starting post-processing of ancestor ACL HREFs.
Cause: Starting post-processing of ancestor ACL HREFs.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14244: Starting post-processing of both resource and ancestor ACL HREFs.
Cause: Starting post-processing of both resource and ancestor ACL HREFs.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14245: Starting post-processing of ACL object.
Cause: Starting post-processing of ACL object.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14246: Post processing successfully completes.
Cause: Post processing of fetcher response was completed successfully.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-14250: Lexical analysis of XML response fails.
Cause: Transitioned to ERROR state in the lexical transition matrix. This condition might be caused by incorrect definitions of state variables or incorrect transition matrix.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14251: The syntax of the XML response is incorrect. Syntax analysis fails (error no: %d).
Cause: The syntax of XML response is wrong and building a syntax tree failed.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14252: The XML response has semantic error or the table/cache update fails.
Cause: There might be two possible reasons: (1) The XML response has semantic errors, so the post-processing function could not understand the response and extract necessary authentication data or ACL data from the response. (2) The post-processing function received all the data from the response, but failed upon updating password verifier, user groupmembership, ACL HREFs, or ACL object.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14260: No user groupmembership inserted. Data validation fails.
Cause: Oracle Web Cache failed in post-processing and insertion of user group membership. Possible reasons include but may not be limited to: 1) Server did not send a valid response. 2) There is syntax or semantic error in the response. 3) The special Oracle Web Cache user was not configured to have sufficient privileges.
Action: Check related server configuration and resources.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14261: The HREF list is incomplete. Data validation fails.
Cause: Oracle Web Cache could not insert all resource ACL HREF and ancestor ACL HREFs to the HREF list. Possible reasons include but may not be limited to: 1) Server did not send complete HREF list. 2) There is syntax or semantic error in the response. 3) The special Oracle Web Cache user was not configured to have sufficient privileges.
Action: Check related server configuration and resources.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14262: The HREF list is empty. Data validation fails.
Cause: Oracle Web Cache could not get the HREFs from the server or the response has syntax/semantic error. Possible reasons include but may not be limited to: 1) Server did not send valid response. 2) There is syntax or semantic error in the response. 3) The special Oracle Web Cache user was not configured to have sufficient privileges.
Action: Check related server configuration and resources.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14263: Some ACL objects have not been parsed. Data validation fails.
Cause: There is a syntax or semantic error in the ACL object. Oracle Web Cache could not parse it.
Action: Check server ACL objects.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14300: Empty resource HREF header or bad HREF format (%s).
Cause: The server sent an empty X-Oracle-Resource-Acl-Href header or the format of the HREF string is invalid.
Action: Check the X-Oracle-Resource-Acl-Href header in the origin server's response.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-14301: Empty resource ancestor HREF header or bad ancestor href format (%s).
Cause: The server sent an empty X-Oracle-Ancestor-Acl-Hrefs header or the format of the ancestor HREF string is invalid.
Action: Check the X-Oracle-Ancestor-Acl-Href header in the origin server's response.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15000: Requested resource has been moved permanently.
Cause: The requested resource was assigned a new permanent URI. Any future references to this resource should use the returned URI.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15001: Requested resource has been moved temporarily.
Cause: The requested resource temporarily resided under a different URI.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15002: Oracle Web Cache generates an HTTP 200 OK status code for a request with an Oracle-Web-Cache-Ping header.
Cause: The request completed successfully.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15003: Cache entry requires validation. The request will be forwarded to the origin server with a validation clause added.
Cause: Cache entry is marked to require validation. Oracle Web Cache will add a conditional validation header "Oracle-Oracle Web Cache-Validate" to the request, listing the content information it has in the cache, and forward the modified request to the origin server. The origin server can respond with a full response, or a 304 Not Modified response to indicate to Oracle Web Cache that certain cached content can be used to service the request.
Action: No action required

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15004: Invalid regular expression found in User-Agent remap rule. %s
Cause: The remap rule contained an invalid regular expression that could not be compiled.
Action: Correct the regular expression in the remap rule.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-15005: Parse error on URL: %.*s - invalid URL but continuing with processing
Cause: The input URL was invalid. Oracle Web Cache continued processing, but the origin server probably returned a bad request (400) response.
Action: Ensure that the URL uses valid HTTP syntax.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15006: Problem normalizing '%.*s'; continuing with original value
Cause: Attempt to normalize the input string failed.
Action: Ensure user supplied URI or host name is properly HTTP encoded.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15101: Address resolution of Oracle Web Cache's listening endpoint \"%s\" fails.
Cause: There was a problem in DNS.
Action: Check DNS configuration on the local machine.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-15102: CRL directory does not exist.
Cause: CRL is enabled for one of the listening endpoints, but the CRL directory does not exist.
Action: Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Configuration

WXE-15300: Request for cached document is denied
Cause: The request sender was not authorized to access the object.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15400: An orcl_wx_repost parameter is found with a non-GET request.
Cause: The request URL contained the special orcl_wx_repost parameter, but the request method was not a GET. The parameter will be stripped and the request processed as a regular request.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15402: The orcl_wx_repost parameter is invalid.
Cause: The request URL contained the special orcl_wx_repost parameter, but its value was empty or invalid. It will be stripped from the URL, the request will be converted to a POST request with an empty body, and an additional request header Oracle-Oracle Web Cache-RePOST with the special value of UID=failed-restore will be sent to the origin server.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15403: Forwarding the restore POST request to the owner cache of the POST data
Cause: This cache was not the owner of the POST data specified by the request. The request will be forwarded as is to the owner cache.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15404: Failed to find POST data with key %.*s.
Cause: The POST data entry specified by the request was not found in the cache. It is either expired or the cache key was invalid. The orcl_wx_repost parameter will be stripped from the URL, the request will be converted to a POST request with an empty body, and an additional request header Oracle-Oracle Web Cache-RePOST with the special value of UID=failed-restore will be sent to the origin server.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-15405: POST data successfully restored.
Cause: Cache lookup of the POST data entry specified by the request was successful. The request has been converted to POST with the looked up POST content. The URL parameter orcl_wx_repost will be stripped and the restored request will be forwarded to the origin server.
Action: No action required.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-15406: The orcl_wx_sid parameter is invalid.
Cause: The request URL contained the special orcl_wx_sid parameter, but its value was empty or invalid. It will be stripped from the URL, and the request will be treated as it would be without the parameter.
Action: No action required.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-17001: A duplicate POST data cache insertion is found with key %.*s. POST data cache insertion fails.
Cause: An existing POST data cache entry existsed with the same key as the current one.
Action: Check the origin server to ensure no duplicate keys are sent for POST data records.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-17005: POST data cache insertion failed with key %.*s because the POST data is too large.
Cause: POST data was too large.
Action: Edit webcache.xml and find the POSTBODYCACHE element under the GENERAL element. Increase the MAXCACHEABLESIZE attribute to the desired value.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-17101: No matching cookies are found for cookie caching.
Cause: No cacheable cookies were found in the response.
Action: See the Oracle Access Manager Integration Guide.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-17102: A duplicate cookie cache insertion is found with key %.*s. Cookie cache insertion fails.
Cause: An existing cookie cache entry existed with the same key as the current one. This could be caused by concurrent requests from the same browser.
Action: See the Oracle Access Manager Integration Guide.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-17110: Previously saved cookies are added to the request.
Cause: A cookie record associated with the user was found and the cookies saved in the record were added to the request.
Action: See the Oracle Access Manager Integration Guide.

Level: 1

Type: TRACE

Impact: Requests/Responses

WXE-17112: Cookie cache is enabled with no SSL enabled listen ports for browser requests.
Cause: The cookie cache feature only works for requests made over SSL connections. The configuration contained the switch that enables cookie caching but no listen ports for browser requests are SSL enabled.
Action: See the Oracle Access Manager Integration Guide.

Level: 16

Type: ERROR

Impact: Requests/Responses

WXE-17113: Oracle Web Cache encountered an error while obtaining SSL session ID for cookie cache operations. NZE-%d
Cause: While trying to retrieve the SSL session ID needed by the cookie cache, an error occured. Cookie cache operations for this request will not succeed.
Action: See the Oracle Access Manager Integration Guide.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-19000: Audit initialization failed. Oracle Web Cache starts with audit logging disabled.
Cause: The audit library failed to initialize.
Action: If the problem persists, contact Oracle Support.

Level: 1

Type: WARNING

Impact: Requests/Responses

WXE-20101: Open socket fd=%d exceeded FDArr_Size %d.
Cause: Potential file descriptor leakage.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-20150: Failure in scheduling asynchronous task: %s.
Cause: Potential memory shortage. Note: This is for all asynchronous functions.
Action: This message is no longer used as of Oracle Fusion Middleware 11g. Contact Oracle Support.

Level: 1

Type: ERROR

Impact: Requests/Responses

WXE-21271: Member cache ID is invalid (id=%d), %s.
Cause: This is a potential logic error. Param %s Desiree where the error happens
Action: Contact Oracle Support.

Level: 8

Type: INTERNAL_ERROR

Impact: Requests/Responses