Last updated on NOVEMBER 01, 2016
Applies to:Web Cache - Version 184.108.40.206.0 to 220.127.116.11.0 [Release Oracle11g]
Oracle Solaris on SPARC (64-bit)
Checked for relevance for 27-Dec-2013
Two nodes of Oracle Fusion Middleware 11g are installed on Oracle Solaris on SPARC (64-bit).
Oracle Web Cache is installed as component of the first node (node1) and mapped to 2 origin servers that are 2 Oracle HTTP Servers installed on node1 and node2.
Oracle WebCache is configured as a software load balancer by adding ROUTINGONLY="YES" as described here to load balance the requests between HTTP Server 1 (node1) and HTTP Server 2 (node2).
The HTTP Server which is installed on the second node (node2) was stopped to test the fail over scenario, some requests are failing with:
There was no response from the application web server for the page you requested.
Please notify the site's webmaster and try your request again later.
The following errors is reported in Web Cache event_log:
[2010-04-05T15:12:58+01:00] [webcache] [ERROR:32] [WXE-11385] [frontend] [ecid: 819931884595,0] The request fails because the service is unavailable.
This only happens if the application was accessed using Web Cache which is installed on the first node (node1), and the request was directed to the second HTTP Server which is installed on the second node (node2):
Client --> WebCache (node1) --> HTTP Server 2 (node2)
In Health Monitor page from Webcache Manager (node1), the origin server HTTP Server (node2) status is "UP" which is incorrect status.
The issue did not reproduce if the second HTTP Server (node2) is up while the first HTTP Server (node1) is down. In this case the WebCache will detect the status of the origin server correctly.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms