Hi there, I am setting up an apache 2.2 reverse proxy, that should use a connection pool to connect to the backend. Unfortunately, there is no connection pool in sight anywhere.
On bugzilla, there are some issues with this connection pooling, but I understand this should not affect me in the most simple setup. Still I am not getting this to work, so there must be some flaw in my configuration, but I can not seem to find it. I am working on debian (sarge!) with a custom compile apache 2.2.8, worker mpm. The backend is a 2.2.6 prefork. The boiled down rp config: ----------------------------------------------------------------------- ServerRoot /data/custom-apaches/apache-2.2.8-worker User www-data Group www-data ServerTokens Prod ServerSignature Off UseCanonicalName On TraceEnable Off HostnameLookups Off PidFile logs/httpd.pid LockFile logs/httpd.lock KeepAlive On KeepAliveTimeout 10 MaxKeepAliveRequests 100 MaxClients 150 Listen 80 LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so LogLevel debug ErrorLog logs/error.log ProxyPass / http://backend-host/ min=5 ----------------------------------------------------------------------- The mod_proxy documentation states: "Setting min will determine how many connections will always be open to the backend server." Now when I start the reverse proxy, there is no connection to the backend. Tcpdump does not show me anything. Netstat remains empty for the destination in question. I enabled mod_status, but it did not show me anything either. (Not sure it would, though.) My error.log shows the following: [Fri Feb 01 13:36:32 2008] [notice] Apache/2.2.8 (Unix) configured -- resuming normal operations [Fri Feb 01 13:36:32 2008] [info] Server built: Feb 1 2008 13:09:30 [Fri Feb 01 13:36:32 2008] [debug] worker.c(1740): AcceptMutex: sysvsem (default: sysvsem) [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1670): proxy: grabbed scoreboard slot 0 in child 16517 for worker http://backend-host/ [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1761): proxy: initialized worker 0 in child 16517 for (backend-host) min=5 max=25 smax=25 [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1670): proxy: grabbed scoreboard slot 1 in child 16517 for worker proxy:reverse [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1761): proxy: initialized worker 1 in child 16517 for (*) min=0 max=25 smax=25 [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1670): proxy: grabbed scoreboard slot 0 in child 16516 for worker http://backend-host/ [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1689): proxy: worker http://backend-host/ already initialized [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1761): proxy: initialized worker 0 in child 16516 for (backend-host) min=5 max=25 smax=25 [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1670): proxy: grabbed scoreboard slot 1 in child 16516 for worker proxy:reverse [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1689): proxy: worker proxy:reverse already initialized [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1761): proxy: initialized worker 1 in child 16516 for (*) min=0 max=25 smax=25 [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1670): proxy: grabbed scoreboard slot 0 in child 16519 for worker http://backend-host/ [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1689): proxy: worker http://backend-host/ already initialized [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1761): proxy: initialized worker 0 in child 16519 for (backend-host) min=5 max=25 smax=25 [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1670): proxy: grabbed scoreboard slot 1 in child 16519 for worker proxy:reverse [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1689): proxy: worker proxy:reverse already initialized [Fri Feb 01 13:36:32 2008] [debug] proxy_util.c(1761): proxy: initialized worker 1 in child 16519 for (*) min=0 max=25 smax=25 I have no previous experience with this connection pooling, so I can't tell if there is anything abnormal. Severity is all debug, so I guess it's okay. When I carry out a request, it works fine and the connection to the backend remains open until the http keepalive expires. Then the connection goes away again. So where is the flaw? Any comment is appreciated. regards, Christian -- Christian Folini, Swiss Post IT, Unix / Apache Engineering +41 (0)58 338 79 96 [EMAIL PROTECTED] --------------------------------------------------------------------- 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: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
