Oracle iPlanet Web Server 7.0.x Reverse Proxy Fails To Notice When An Out-Of-Service Origin Server Restarts and Throws Error HTTP7751

(Doc ID 1344495.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle iPlanet Web Server - Version 7.0 and later
Information in this document applies to any platform.
***Checked for relevance on 20-Jan-2014***

Symptoms

The Web Server is configured to reverse proxy the URI /testpages to two Origin Servers, as shown in the following line from the <vs>-obj.conf:

<Default>
.
.
NameTrans fn="map" from="/testpages" name="reverse-proxy-/testpages" to="http:/testpages"
.
.

<Object name="reverse-proxy-/testpages">
Route fn="set-origin-server" sticky-cookie="JSESSIONID" route-cookie="JROUTE" sticky-param="jsessionid" route-hdr="Proxy-jroute" rewrite-location="true" rewrite-content-location="true" server="origin1:1234" server="origin2:1234"
</Object>


When one of the Origin Servers goes offline, the RP notices this and marks it as offline. This is shown in the error log:

[28/Jul/2011:13:15:46] info ( 6403) vs1-reverse-proxy: for host 1.2.3.4 trying to GET /testpages/index.html, set-origin-server reports: HTTP7751: server origin2:1234 offline


However, when the Origin Server comes back online, it's not noticed by the RP and requests are not directed to this Origin Server.

Cause

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