httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46231] New: Connection Pooling with ajp depends on syntax ?
Date Tue, 18 Nov 2008 17:33:10 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46231

           Summary: Connection Pooling with ajp depends on syntax ?
           Product: Apache httpd-2
           Version: 2.2.10
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: major
          Priority: P2
         Component: mod_proxy
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: giesyntm@yahoo.com


Hello,

I think there's a bug with mod_proxy_ajp and connection pooling. I explain
myself ...

I've run some tests with brand new Apache 2.2.6 and 2.2.10 instalations.
After that I enable mod_proxy and mod_proxy_ajp and add these lines :

ProxyRequests Off
ProxyPass /servlets-examples/servlet/HelloWorldExample
ajp://localhost/servlets-examples/servlet/HelloWorldExample

There's a Tomcat 5.5.25 as the backend server with AJP 8009 port open

Then I use JMeter to pound on the same Servlet, ever and ever, with 10 threads.

Apache opens a socket for every HTTP requests and closes it causing a
TIME_WAIT.
When too many ports are on TIME_WAIT, Apache cannot create new sockets and this
comes to an error in the error.log and a 503 "server too busy" for the user
browser.

Apache can't stand this treatment for more than 30 secs before causing 503s.

Then starts the weird thing :

When I change the proxyPass line with this :
ProxyPass /servlets-examples/servlet/HelloWorldExample
ajp://localhost:8009/servlets-examples/servlet/HelloWorldExample

There's no more problem !!! No TIME_WAIT ... connection pool is used ... only
10 ESTABLISHED connections ... It's a kind of magic for me ...

This is a simple example to reproduce the "bug" but I have the same TIME_WAIT
503 bug with another Servlet Name even with the :8009 port specified ...
I've tried to mess with the pool settings with no more luck than letting the
default (no specifiing pool params)

for testing how many TIME_WAIT I have I use "netstat -an | find ":8009" | find
/c "TIME"
This command is supposed to return always 0 if the connection pool is used.

This behaviour is reproduced on XP too.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message