[users@httpd] mod_proxy and intermittant 502s - is my config incorrect?

[Dmitri Colebatch <di...@colebatch.com>]

Hi all,

I'm trying to track down an intermittant problem with our apache
servers where they intermittantly serve 502 responses when I believe
they should be able to contact the server.  Our situation is that we
have apache sitting in front of BEA Weblogic (both 8.1 and 9.1).  We
are simply using apache for some re-writes and a few other bits and
pieces and generally it works very well.  However we frequently
experience bouts of 502s being served, when I believe that WL is
available to serve requests.

We're running 2.0.46 on redhat and have attempted to fix this problem
by turning off keepalives by setting force-proxy-request and
proxy-nokeepalive.  However I'm not 100% sure what I've done is
working.  As we have several virtual hosts and they all experience
this problem I want to apply this globally and so have created a file
/etc/httpd/conf.d/__proxy_1_0.conf which is then included in the
configuration and used for each virtual host (I hope).  Here's some
details on our config:

[bea@toyibuspf1 conf.d]$ ll
total 20
-rw-r--r--    1 bea      bea           460 Oct 19 16:40 access.conf
-rw-rw-r--    1 bea      bea           139 Oct 20 14:17 __proxy_1_0.conf
-rw-r--r--    1 bea      bea           355 Feb 20 11:10
schemas.autodesa.org.conf
-rw-r--r--    1 bea      bea           657 Feb 20 11:10 track.toyota.com.au.conf
-rw-r--r--    1 bea      bea          2076 Feb 20 11:10
_webservices.toyota.com.au.conf

[bea@toyibuspf1 conf.d]$ cat __proxy_1_0.conf
# See http://issues.apache.org/bugzilla/show_bug.cgi?id=37770 for reference

SetEnv force-proxy-request-1.0 1
SetEnv proxy-nokeepalive 1

The other config files are all pretty straight-forward virtual hosts.
Am I wrong in thinking that this proxy config will be included and
used as I'm hoping?  Would I be better off renaming it to proxy.incl
and including it in each virtual host itself?  Looking at
http://httpd.apache.org/docs/2.0/mod/mod_proxy.html#envsettings it
would seem to suggest that the SetEnv directives need to be inside the
same location block as the ProxyPass directive however the SetEnv docs
( http://httpd.apache.org/docs/2.0/mod/mod_env.html#setenv) say it can
be applied at various levels.  I'm assuming that applying it at the
top level will cascade down, is this the case?  For the record, my
location blocks look like:

        <Location /ibus>
                ProxyPass http://localhost:7501/ibus
                ProxyPassReverse http://localhost:7501/ibus
                Allow from All
        </Location>

Any suggestions or pointers would be gratefully appreciated.

cheers
dim

---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org