E
Event Log Messages

Startup Initialization Events

Listening on ADMINISTRATOR port port address ip_address

Oracle9iAS Web Cache is accepting administration requests on the specified listening port number and IP address.

Listening on INVALIDATION port port address ip_address

Oracle9iAS Web Cache is accepting invalidation requests on the specified listening port number and IP address.

Listening on NORM port port address ip_address

Oracle9iAS Web Cache is accepting Web browser requests on the specified listening port number and IP address.

Listening on STATISTICS port port address ip_address

Oracle9iAS Web Cache is accepting statistics monitoring requests on the specified listening port number and IP address.

The cache server is started by the admin server at startup

The Oracle9iAS Web Cache admin server process started the cache server process.

The admin server started successfully

The Oracle9iAS Web Cache admin server process successfully started.

Auto-Restart: WXE-00800 Auto-restart started successfully

The Oracle9iAS Web Cache auto-restart process successfully started

The cache server started successfully

The Oracle9iAS Web Cache cache server process successfully started.

SSLInitialize: Origin Server Wallet file file does not exist

Oracle9iAS Web Cache is unable to open the wallet file intended for HTTPS requests to origin servers.

See Also: "Wallet Cannot Be Opened"

SSLInitialize: Wallet file file does not exist

Oracle9iAS Web Cache is unable to open the wallet file intended for HTTPS requests to Oracle9iAS Web Cache or its operations ports.

See Also: "Wallet Cannot Be Opened"

SSLInitialize: Wallet Autologin file file does not exist - Wallet does not appear to be autologin wallet

SSLInitialize: Origin Server Wallet Autologin file file does not exist - Wallet does not appear to be autologin wallet

Oracle9iAS Web Cache is unable to open the wallet without a password. Oracle9iAS Web Cache requires auto-login of wallets.

See Also: "Wallet Cannot Be Opened"

Shutdown Events

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

A UNIX event that specifies that Oracle9iAS Web Cache will shut down once all connections are complete.

The server is exiting

Oracle9iAS Web Cache is shutting down.

Operational Events

There was a network failure before the transaction was completed

Oracle9iAS Web Cache terminated a connection to the Web browser.

Invalidation Events

<Invalidation>Exact URI URI has been invalidated successfully

The URL is successfully invalidated.

<Invalidation>Invalidation sent upstream to webcache host 'web_cache_hostname'port 'port' has returned with response code: 'response_code'.

In a ESI cache hierarchy, the provider cache is unable to connect to the subscriber cache.

<Invalidation>Invalidation with info 'INFO_comment' has returned with status 'status'; number of documents invalidated: 'number'

The result of the invalidation. INFO_comment is the comment specified in the INFO element of the invalidation request. status is one of the following:

• SUCCESS for successful invalidations

• URI NOT CACHEABLE for documents that are not cacheable

• URI NOT FOUND for documents not found

number is the number of documents invalidated during the invalidation request.

<Invalidation>Requested URI URI is not found in the cache. URI is not invalidated

The URL is not in the cache and cannot be invalidated.

<Invalidation>URI URI is not cacheable

The URL is not a cacheable document and cannot be invalidated.

<Invalidation>number URLs with prefix prefix have been successfully invalidated

The number of URLs by a particular prefix that have been successfully invalidated.

<Invalidation>Subscriber host 'web_cache_hostname' port 'port' has been removed due to exceeded failure count.

In a hierarchy of Oracle9iAS Web Cache servers, the invalidation provider's connection to the invalidation subscriber has failed more than three times.

Cache Cluster Event

A number node cluster successfully initialized

Oracle9iAS Web Cache started the cache cluster with the specified number of cache cluster members.

Startup Initialization Events

The admin server couldn't start the cache server, running in admin-only mode

The admin server process is unable to start the cache server process. This may due to a listening port conflict.

Auto-Restart:WXE-08505 number consecutive error(s) pinging the cache server. number error(s) required for restart.

The auto-restart process encountered an error when polling the cache server process,

Origin Server Wallet Failed to open at location location.

Oracle9iAS Web Cache is unable to open the wallet intended for HTTPS requests to the origin server.

See Also: "Wallet Cannot Be Opened"

Warning: SSLInitialize: Orgin Server Wallet did not open -- Operating without wallet for backend

Oracle9iAS Web Cache will use HTTPS for requests to the origin server without a wallet.

See Also: "Wallet Cannot Be Opened"

Wallet Failed to open at location location -- Opened wallet as user=user. -- Please verify wallet location and Auto Login support enabled.

Oracle9iAS Web Cache found the wallet, but is unable to open the wallet without a password. Oracle9iAS Web Cache requires auto-login of wallets.

See Also: "Wallet Cannot Be Opened"

Memory-Related Events

No space left for adding the Content-Length header for KeepAlive headers URI: URI

Oracle9iAS Web Cache does not have enough memory to allocate memory for Keep-Alive headers.

For each response from the application Web server that does not contain a Content-Length field in the header, Oracle9iAS Web Cache allocates extra memory for Keep-Alive headers.

Response cookie header too large

The response cookie from the origin server is too large for Oracle9iAS Web Cache.

Origin Server Events

<Admin Server>Concurrent administration exceeded limit

The number of concurrent connections (capacity) to the origin servers has been exceeded

Connect Failed: Origin Web Server not accepting Connection

The origin server is not accepting connections from Oracle9iAS Web Cache. This event could indicate that the origin server is down.

Last-Modified time time is AFTER current time time, using current time instead

The Last-Modified field in the response header is after the current time. Oracle9iAS Web Cache will use the current time instead.

Origin Server module got an ABORT; Errno: error_number URI: URI

Oracle9iAS Web Cache detects a problem with the origin server. error_number can be one of the following:

3 - low memory

There is not enough system memory for the webcached executable to run.

4 - LB fail

All of the origin servers are down, disabling the load balancing feature.

5 - no application server mapping. dynamic os not allowed

The error appears in either of the following situations

--The site is not defined.

--This virtual host site is not mapped to any origin servers.

To create a site definition, use the Site Definitions page (General Configuration > Sites) of Oracle9iAS Web Cache Manager. To map a site to application Web servers or proxy servers, use the Site to Server Mapping page (General Configuration > Site to Server Mapping) of Oracle9iAS Web Cache Manager.

6 - socket connect fail

The origin server is down.

7 - socket create fail

The Oracle9iAS Web Cache computer has run short of system resources.

8 - send request fail

The request to the origin server has failed.

9 - bad input stream to send

Oracle9iAS Web Cache is unable to send the HTTP request body to the origin server.

10 - recv fail

Oracle9iAS Web Cache is unable to receive responses from the origin server.

11 - create header fail

Oracle9iAS Web Cache is unable to process the HTTP response header message from the origin server.

12 - header too big

The HTTP response header message from the origin server is too large.

13 - ct buffer too small

There is not enough system memory.

14 - ssl hand shake fail

The SSL hand shake between Oracle9iAS Web Cache and the origin server failed.

16 - ESI https mismatch

The protocol supported by origin server does not match the protocol specified in the src attribute of the <esi:include> tag.

For example, if the src is http://www.company.com/frag1 and www.company.com is a defined HTTPS origin server, then this message appears. You must change the src attribute to https://www.company.com/frag1.

17 - create request fail

Oracle9iAS Web Cache failed to create a request to the origin server.

18 - dynamic OS DNS fail

The DNS lookup for the ESI provider site failed. This can occur for the following reasons:

--There is system memory problem with the Oracle9iAS Web Cache computer

--The ESI provider site is down or does not exist

19 - dynamic OS connect fail

Oracle9iAS Web Cache received the DNS lookup result, but was unable to connect to the ESI provider site.

20 - header operation fail

Oracle9iAS Web Cache cannot manipulate the HTTP response header from the origin server. This occurs if the Oracle9iAS Web Cache computer is experiencing a system memory problem.

21 - OS request dropped

Oracle9iAS Web Cache cannot forward requests to the origin server. This occurs if the origin server has reached its capacity and the queue for new request is full.

22 - proxy authentication failed.

The authentication to the proxy server failed.

23 - proxy authentication failed for CONNECT

The proxy server denied the request.

24 - network error sending CONNECT to proxy

Oracle9iAS Web Cache encountered a network error sending a CONNECT message for opening an SSL connection to the proxy server. A CONNECT message open an SSL connection through the proxy.

25 - network error receiving response to CONNECT

Oracle9iAS Web Cache encountered a network error receiving a CONNECT message to the proxy server.

26 - proxy sent unrecognized response to CONNECT

Oracle9iAS Web Cache did not recognize the CONNECT response message sent by the proxy server.

Expiration time beyond year 2038, setting to MAX_LONG

time time overflow, setting to MAX_LONG

The time set for the document goes beyond the year 2038, which is the maximum time limit on Sun Solaris.

Cache Cluster Events

Add Cluster member# cluster_ID

Oracle9iAS Web Cache added the cache cluster member to the cache cluster.

Cluster Member sent invalid configuration error

A bad configuration response header was returned from a request. However, this request was not a Oracle9iAS Web Cache cluster peer request.

Cluster member# cluster_ID already marked alive

An attempt to mark the cache cluster member as active and running has been made. However, a previous concurrent request has already noted the member as being active and running.

Cluster member# cluster_ID already marked dead

An attempt to mark the cache cluster member as being inactive or down has been made. However, a previous concurrent request has already noted the member as being inactive or down.

Cluster Member cluster_ID down. Start pinging.

Oracle9iAS Web Cache detects a cache cluster member is down, and it starts to poll the member by sending requests a configured URL.

Cluster Member cluster_ID up. Stop ping.

Oracle9iAS Web Cache received a success response from the downed cache cluster member. Oracle9iAS Web Cache considers the cache cluster member to up again. It recalculates the relative capacity of the cache cluster members, and it reassigns ownership of cache content.

Cluster Member cluster_ID - cluster_name configuration is invalid.

The cache cluster member sent a message to Oracle9iAS 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. To resolve this error, compare the two configuration files, and then propagate the proper version to all cluster members.

Cluster Member cluster_ID - cluster_name configuration is valid.

The cache cluster member was previously excluded from the cluster due to a configuration file that was different than the local view. The configuration files between these two members are now consistent.

Cluster Member cluster_ID - cluster_name sent invalid configuration error.

The cache cluster member sent a response to Oracle9iAS 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. To resolve this error, compare the two configuration files, and then propagate the proper version to all cluster members.

Remove Cluster member# cluster_ID

Oracle9iAS Web Cache removed the cache cluster member from the cache cluster.

Unknown Cluster Member sent invalid configuration error.

The cache cluster member sent a response to Oracle9iAS Web Cache that indicates it has a configuration file different than the local configuration file for the cache cluster. Additionally, this peer member cache is not specified in the local webcache.xml configuration file. A cluster runtime operates with the same webcache.xml configuration file for all members. To resolve this error, compare the two configuration files, and then propagate the proper version to all cluster members.

Startup Initialization Events

Failed to start the server

Oracle9iAS Web Cache is unable to open listening ports.

Oracle Web Cache cache failed to initialize

Oracle9iAS Web Cache is unable to initialize the cache server process.

The server could not initialize

Oracle9iAS Web Cache is unable to start.

The server could not start service thread

Oracle9iAS Web Cache encountered a thread initialization creation error.

An error occurred scanning the directory directory.

Oracle9iAS Web Cache is unable to load the Oracle9iAS Web Cache Manager help files or icons.

Could not increase number of file/socket descriptors to connections

Oracle9iAS Web Cache is unable to support the number connections. Adjust the number of maximum incoming in the Resource Limit page (Cache-Specific Configuration > Resource Limits) of Oracle9iAS Web Cache Manager.

See Also: "Greater Than One Thousand Maximum Connections"

Startup Initialization Events Related to Auto-Restart Process

Auto-Restart:WXE-08500 Cache server not responding on port port.

The Oracle9iAS Web Cache server may not be running.

Auto-Restart:WXE-08501 Timeout occurred communicating with the cache server.

Oracle9iAS Web Cache is either in an unstable state or slow responding to queries.

Auto-Restart:WXE-08502 Lost connection with the cache server

There were communication errors between the auto-restart process and the cache server process.

Auto-Restart:WXE-08503 Operating system level error in function error_number: error_message.

The auto-restart process encountered a system call returned error.

Auto-Restart:08504 number consecutive errors pinging the cache server.

The number of consecutive failed requests to the cache server process that the auto-restart process has sent.

Set the number of failed consecutive request in the Auto-Restart page (General Configuration > Auto-Restart) of Oracle9iAS Web Cache Manager.

See Also: "Task 6: Configure Auto-Restart Process Settings"

Auto-Restart:WXE-08506 Unable to read cache server pid file. Stopping the cache monitor.

The auto-restart process is unable to read the webcache.pid file to determine the process ID of the cache server process. Most likely the file was deleted during a normal termination of the server.

Auto-Restart:WXE-08507 Cache server process not running.

There is no process on the system matching the process ID listed in the webcache.pid file.

Auto-Restart:WXE-08508 Restarting the cache server.

The auto-restart process is restarting the cache server process.

Auto-Restart:WXE-08509 Starting the cache server.

The auto-restart process is starting the cache server process.

Failed to start the auto-restart monitor. failure_reson.

The cache server process is unable to start the auto-restart process.

Read/Write Events

Could not open config file (config_file)

Oracle9iAS Web Cache is unable to write to its configuration file due to a permissions problem.

Could not open log file (access_log)

Oracle9iAS Web Cache is unable to write to its access log file due to a permissions problem.

UNIX Process Identity Events

Failed to find User (user) in /etc/password

Invalid User ID (user)

The current user cannot perform this operation. Only the root user or the user specified in the Process Identity page (Cache-Specific Configuration > Process Identity) of the Oracle9iAS Web Cache Manager can perform this operation.

Failed to find Group (group) in /etc/group

Invalid Group ID (group)

The group ID that the current user is a member of is not valid for this operation.

Permission denied when setting User ID (user)

The current user that is being set is not the owner of the Oracle9iAS Web Cache executables and is not the root user.

Permission denied when setting Group ID (group)

The current group that is being set is not the owner of the Oracle9iAS Web Cache executables.

Memory-Related Events

Cache failed to allocate memory for the hash table

Oracle9iAS Web Cache is unable to allocate memory for cache initialization.

Cache Index memory allocation error

Oracle9iAS Web Cache is unable to allocate memory for cache initialization.

Document compression error: error

Oracle9iAS Web Cache is unable to compress the document in its cache.

Insert failed (memory low during insertion) for slave document document

Oracle9iAS Web Cache is unable to insert a document into its cache.

Out of memory

Oracle9iAS Web Cache is out of cache memory. Adjust the cache memory in the Resource Limits page (Cache-Specific Configuration > Resource Limits) of Oracle9iAS Web Cache Manager.

Process out of memory on malloc/realloc request. Exiting process.

Oracle9iAS Web Cache is out of cache memory. Adjust the cache memory in the Resource Limits page (Cache-Specific Configuration > Resource Limits) of Oracle9iAS Web Cache Manager.

The system has run critically low on memory

This error indicates that insufficient virtual memory remains in the cache server process to satisfy the request. The error can be caused by either of the following situations:

• The request is for an inordinate amount of memory, thus causing the system limit for virtual memory to be exceeded.

• The cache's memory is extremely full and this request puts the cache server process over the system limit.

When this error occurs, the cache server process is stopped. If auto-restart is enabled, then the auto-restart process automatically restarts the cache server process. If auto-restart is not enabled, then restart the cache server process from the Operations page (Administration > Operations).

Operational Events

Invalid XLF Field Name: user_field

The user-specified field specified for the access log file is invalid. The fields are specified in the Access Logs page (Cache-Specific Configuration > Access Logs) of Oracle9iAS Web Cache Manager.

Too many session definitions

The number of allowed session definitions used for cacheability rules for pages with personalized attributes or session tracking has exceed the 20 name limit. Reduce the name of session names in Session/Personalized Attribute Definitions (General Configuration > Session Management > Session/Personalized Attribute Definitions) page of Oracle9iAS Web Cache Manager.

Origin Server Events

Unable to resolve the IP address of ip_address. Check your DNS setup.

Oracle9iAS Web Cache is unable to resolve the IP address of the origin server. You can alter origin server configuration in the Application Web Servers page (General Configuration > Application Web Servers) or the Proxy Server page (General Configuration > Proxy Servers) of Oracle9iAS Web Cache Manager.

This product only supports IPv4 for origin server ip_address. Check your DNS setup

Oracle9iAS Web Cache supports IP version 4. The IP address of the origin server cannot be resolved because it uses another version of the IP.

Invalidation Events

<Invalidation>Cannot compose key pattern for the requested URI URI

The URL specified in the invalidation message does not have a corresponding cacheability rule.

<Invalidation>Check ClientIP failed. Access denied

The computer from which the invalidation message came from is not a trusted host. You configure trusted hosts in the Security page (General Configuration > Security) of Oracle9iAS Web Cache Manager.

<Invalidation>Default URL size too small for cache key

The URL specified in the invalidation message is too long. Oracle9iAS Web Cache has a 3 KB limit on URLs that may or may not include cookies or HTTP request headers.

<Invalidation>Empty entity

The invalidation message is empty.

<Invalidation>Invalid validity level (valid range is 0-9). Level=level.

The validity level specified in the invalidation message is not valid.

<Invalidation>Not an invalidation request

The message is not an invalidation message.

<Invalidation>Unrecognized cookies in the invalidation message

The cookies specified in the invalidation message are not valid.

<Invalidation>URL Node reading error

The URL specified in the invalidation message is invalid or or there is a memory allocation problem.

<Invalidation>Username/password check failed. Access denied.

The invalidation user name and password is not valid. The invalidation user is invalidator. By default, the password is invalidator. You can change the password in the Security page (General Configuration > Security) of the Oracle9iAS Web Cache Manager.

<Invalidation>XML parsing error

The invalidation message uses invalid XML syntax.

Cache Cluster Events

Cache memory allocation for the cluster configuration block

Oracle9iAS Web Cache ran out of memory on the system.

Cache memory allocation for the cluster member table

Oracle9iAS Web Cache ran out of memory on the system.

Cluster member count count is larger than maximum allowed 99

The number of cache cluster members specified in the cache cluster configuration is larger than the maximum limit of 99.