Actually, without the Proxy, the WAS plugin properly detects an instance as being down and reroutes the requests to one of the other app servers. So, with the proxy, it keeps sending requests to the faulty server causing people to see frequent "bad gateway errors". But, you are correct when dealing with an environment that only has one appserver that is down, or dealing with an environment with multiple app servers -- all of which are down. So, in my my multi-app server environment, the proxy is basically breaking the plugin's functionality to detect and reroute traffic. --- Axel-Stéphane SMORGRAV <Axel-Stephane.SMORGRAV@xxxxxxxxxxxxxx> wrote: > If it were not for the Proxy server, the user would > just get a "Connection refused" or "Unable to > connect/Connection timed out" which in my opinion is > no better than that HTTP 502 (Bad Gateway). At least > the proxy server gives you the option of serving a > custom error page for the HTTP 502 using the > ErrorDocument directive, explaining to the user that > the server is temporarily unavailable. > > Then of course, if you are using the WebSphere > plugin and you have multiple WAS backends, chances > that no WAS is available at any given time should be > pretty slim... > > -ascs > > -----Original Message----- > From: Richard de Vries > [mailto:richard_devries@xxxxxxxxx] > Sent: Wednesday, June 28, 2006 4:50 AM > To: users@xxxxxxxxxxxxxxxx > Subject: [users@httpd] Reverse Proxy between > WebSphere and the WebServer - prevent "Bad Gateway" > errors. > > I was wondering if anyone on this list has ever > configured a WebSphere environment with a reverse > Proxy (Apache) sitting between the WebSphere App > Server, and the WebServer. > > Why would you want to do that you may ask? The > answer is simple ... to secure the WebSphere > Application Server instance from people trying to > bypass the webservers. > > Basically, I have WAS listening on the 127.0.0.1 > adapter of the server, and have the Proxy Server > listen on the public IP addresses. The proxy server > in turn will proxy the incoming requests from the > public IP to WAS on localhost. > > So far all is well. The problem comes with the > WebSphere WebServer plugins. Since we're running our > WAS in a clustered environment -- the WebSphere > plugin does some loadbalancing and logic to > determine what WAS instance is up. If an instance is > down, it's supposed to send the request to one of > the alternate servers. > > Unfortunately, with the Proxy server in the middle, > the WAS plugin doesn't detect the WAS instance as > being down, because even with the WAS instance down, > the proxy is accepting connections. This then > results in a "Bad Gateway" error. > > Any suggestions on how to circumvent this issue? > > Thank you :-) > > Richard > > > --------------------------------------------------------------------- > The official User-To-User support forum of the > Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for > more info. > To unsubscribe, e-mail: > users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: > users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: > users-help@xxxxxxxxxxxxxxxx > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|