Hi,

I compiled apache 2.0.52 binaries for Linux with mod_proxy (and
others). These binaries have worked well so far in several Linux boxes.
Nevertheless, I am experiences some response time issues with a
specific machine. It takes more than 10 seconds for the reverse proxy
to respond. The machine is a Red Hat AS 2.1 (2.4.9-e.3smp kernel).

>From the error_log you could see what I am describing:

[Thu Mar 17 18:11:56 2005] [debug] proxy_http.c(66): proxy: HTTP:
canonicalising URL //localhost:3002/sfxadmin/sfx_local
[Thu Mar 17 18:11:56 2005] [debug] mod_proxy.c(416): Trying to run
scheme_handler
[Thu Mar 17 18:11:56 2005] [debug] proxy_http.c(1049): proxy: HTTP:
serving URL http://localhost:3002/sfxadmin/sfx_local
[Thu Mar 17 18:11:56 2005] [debug] proxy_http.c(185): proxy: HTTP
connecting http://localhost:3002/sfxadmin/sfx_local to localhost:3002
[Thu Mar 17 18:12:06 2005] [debug] proxy_util.c(1138): proxy: HTTP: fam
2 socket created to connect to localhost
[Thu Mar 17 18:12:06 2005] [debug] proxy_http.c(334): proxy: socket is
connected
[Thu Mar 17 18:12:06 2005] [debug] proxy_http.c(368): proxy: connection
complete to 127.0.0.1:3002 (localhost)
[Thu Mar 17 18:12:07 2005] [debug] proxy_http.c(884): proxy: start body
send
[Thu Mar 17 18:12:07 2005] [debug] proxy_http.c(943): proxy: end body
send

I check the server load, and it looks normal. Is there anything else I
should check?

This is some more info about my server:
Server: Apache/2.0.52, Interface: mod_ssl/2.0.52, Library:
OpenSSL/0.9.7e


Thanks in advance,

---
Andres Monroy-Hernandez
Ex Libris Inc.

Andres Monroy-Hernandez wrote:
> Hi,
>
> I compiled apache 2.0.52 binaries for Linux with mod_proxy (and
> others). These binaries have worked well so far in several Linux boxes.
> Nevertheless, I am experiences some response time issues with a
> specific machine. It takes more than 10 seconds for the reverse proxy
> to respond. The machine is a Red Hat AS 2.1 (2.4.9-e.3smp kernel).

I should check your machine is happy with its own DNS.

I should also play with keepalive timeouts on both the proxy and backend
in case you have an application that has to wait for a connection to
close. Trying it in Lynx might be useful, too.

--
Nick Kew

Thanks.

Indeed, it was a problem with DNS (which I have not figured out). I
changed the reverse proxy configuration from localhost to the actual
name of the server and it works faster.