My Oracle Support Banner

WebCache Is Sending Requests To Origin Servers Not Mapped To The Site Specified In The URL (Doc ID 1312406.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Web Cache - Version 10.1.2.3.2 to 11.1.1.6.0 [Release AS10gR2 to Oracle11g]
Information in this document applies to any platform.

Symptoms

In a WebCache 10.1.2.3.2 / 11.1.1.x environment requests for a given site can be routed sporadically to the wrong origin server. The problem can not be reproduced at will and may fail to reproduce unless the environment has a high concurrency load.

The configuration  is a mix of sites mapped to origin servers using session binding and sites mapped to origin servers not using session binding.

When the problem reproduces Webcache sends the request to an origin server which is NOT mapped to that site. The configuration can contain mappings as follows:

SiteSession Binding ?Origin Server
<HOSTNAME1> N <HOSTNAME2>
<HOSTNAME1> N <HOSTNAME3>
<HOSTNAME4> Y <HOSTNAME5>
<HOSTNAME4> Y <HOSTNAME6>



Setting the log level to DEBUG you see in the $ORACLE_HOME/webcache/logs/event_log (10.1.2) $INSTANCE_HOME/diagnostics/logs/WEBCACHE/webcache1/event_log how a request for <HOSTNAME1> is routed to <HOSTNAME5> or <HOSTNAME6> instead of the expected origin servers, which are <HOSTNAME2> / <HOSTNAME3>.

[17/Feb/2011:14:42:58 +0100] [trace 11220] [ecid: <ECID>] Session binding routing to origin server <HOSTNAME6>:80 (id=9) for site <HOSTNAME1>:80

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.