On Tue, 9 Mar 2004, Steve Hay wrote: > Steve Hay wrote: > > >I'll try chopping some of the new (post _12) tests out to see if I can > >get it working again. > > > If I remove: > > t/htdocs/vhost/startup.pl > t/response/TestVhost/config.pm > t/vhost/config.t > > then run "t/TEST -conf" and then try "nmake test" again, then it's all > OK with 20 threads. > > Increasing ThreadsPerChild to 50 was overkill, though -- it actually > works fine (with the vhost tests back in) with just 21 threads. Looks > like the new vhost tests need 1 extra thread. > > Interestingly, the number of threads required seems to be quite > specific. If I have 20 specified instead of the 21 that it needs then I > get this in the error_log: > > Server ran out of threads to serve requests. Consider raising the > ThreadsPerChild setting > > If I specify 19 threads then I get that error 2 times; if I specify 18 > threads then I get it 3 times; ...if I specify 21-X threads then I get > it X times. > > Without the vhost tests, if I specify 20-X threads then I get the error > X times. > > Is this expected behaviour?
This behaviour was also found about a year or so ago, when some virtual hosts were added to the tests. At that time there seemed to be some correlation between the number of threads required and the number of virtual hosts being used, but if that's so, it's not a simple relationship. Even now, with the default setting, I can run the tests OK "most of the time" without running out of threads. -- best regards, randy -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
