WebCache Is Sending Requests To Origin Servers Not Mapped To The Site Specified In The URL

(Doc ID 1312406.1)

Last updated on FEBRUARY 22, 2017

Applies to:

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


In a WebCache / 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
orange.mydomain.com N orange1.internaldomain.com
orange.mydomain.com N orange2.internaldomain.com
pineapple.mydomain.com Y pineapple1.internaldomain.com
pineapple.mydomain.com Y pineapple2.internaldomain.com

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 orange.mydomain.com is routed to pineapple1.internaldomain.com or pineapple2.internaldomain.com instead of the expected origin servers, which are orange1.internaldomain.com / orange2.internaldomain.com.

[17/Feb/2011:14:42:58 +0100] [trace 11220] [ecid: 388503144827,0] Session binding routing to origin server pineappl2.internaldomain.com:80 (id=9) for site orange.mydomain.com:80


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms