% t/TEST protocol
It seems that the issue may come from Apache, doing a silly thing. It reports:
WARNING: MaxClients (3) is not an integer multiple of ThreadsPerChild (2), lowering MaxClients to 2 for a maximum of 1 child processes,
so if our test suite relies on having 3 clients, we end up with just two. so changing:
<IfModule worker.c>
StartServers 1
MinSpareThreads 2
MaxSpareThreads 2
ThreadsPerChild 2
MaxClients 3
MaxRequestsPerChild 0
</IfModule>to:
MaxClients 4
takes the problem away. So one issue is A-T needs to ensure that
MaxClients % ThreadsPerChild == 0
I think the simplest thing to do is to have ThreadsPerChild == MaxClients, but then we will again hit that MaxClients reached [error] message.
Though I'm not sure why do we need 3 clients for that test. It may indicate that there is some other problem -- some of the tests still have the connections open when that test gets to run, and not letting the clients move on to serve the new requests.
I'm looking into it.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
