> 1. Great suggestion, Don, but no go. I compiled and ran > apache 2.0.46, and it seems to behave the same as apache 1. > So close in every regard that I had to check the server > software reported by 'ab' to make sure I was hitting the > right port. I'm still suspicious.
The default compile of Apache 2 on Unix uses the prefork multi-processing module, which is a preforked, process-based approach that is very similar to the Apache 1.x approach (see http://httpd.apache.org/docs-2.0/mpm.html for more info). To use the threaded behavior, you need to specify "--with-mpm=worker" or "--with-mpm=threadpool". Did you specify a threaded MPM? Have you set maxthreads somewhere above 15? Although you said the test URL was a static HTML file, do you have any filters that might use database connections? If so, are you allowing enough database connections so you're not throttled on them? Do you have filters or other scripts/customizations that would lock around a precious resource? -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
