> Why put minProcessors higher then the maximum allowed ? Think this does make no sense and should result in either a constant ammount of processors (the min value, since it cannot fall lower), an error message at startup or some other, unexpected behaviour. Now I set the minProcessors to 30, maxProcessor to 10. What happens is: No error messages in any log. 8 connections after startup of my prog. 9th connection after two seconds 10th connections after nine seconds. Then with each second a new connection is accepted. (Stopped the prog at 20 connections)
After restarting 18 connections are established directly, two more after some seconds. 50 seconds after starting the program: Connections are interrupted. Logfile says: INFO: All threads are busy, waiting. Please increase maxThreads or check the servlet status10 10. > I'm having trouble finding the exact meaning of some of the parameters > myself... but this might be part of a solution for your problem: > > Why put minProcessors higher then the maximum allowed ? > > Pepijn Palmans > Managing Director > > Kangaroot Linux Solutions > Grote Steenweg 91 > 2600 Antwerp, Belgium > Tel: +32 3/286.17.17 > Fax: +32 3/281.23.49 > > > On Fri, 20 Feb 2004, Christian Hufgard wrote: > > > Hi folks, > > > > did not found this question answered, neither in the faqs, nor in the > > archive of this mailing list, nor in bugzilla. > > > > Like in the subject described, my question is, wether the attribute > > maxProcessors in the Connector tag sets the maximum ammount of > concurrent connections > > the CoyeteConnector handles. > > > > I tested this on Tomcat up to 4.1.24 with jdk 1.4.2 on debian with > kernel > > 2.4.19, since this is our productive environment. If i set up the > connector in > > server.xml with the following parameters: > > > > <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --> > > <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" > > port="8080" minProcessors="20" maxProcessors="10" > > enableLookups="true" redirectPort="8443" > > acceptCount="5" debug="0" connectionTimeout="20000" > > useURIValidationHack="false" disableUploadTimeout="true" > /> > > > > I find a pretty strange behaviour (if maxProcessors should be max > > Connections): > > My test programm (jdk 1.4) tries to open up 80 connections to the tomcat > and > > send some continueus requests to a webapps that create some load on the > > server. The requests use HTTP/1.1 to keep the connection opened and > request a > > page each half second with variing parameters.. > > I would expect, that 15 connections would be opened. 10 active + 5 on > hold. > > What I see is, that normally 18 connections are accepted upon startup of > my > > programm. After 8 seconds another two connections are established, 12 > seconds > > later, again two new connections... This leads up to about 30-40 > > connections. > > > > So, finally I precise my question a bit: What exactly does maxProcessors > > mean? If it does not mean max concurrent connections, how many > connections can > > one processor handle? > > > > Hope I could describe my problem fairly enough :) > > > > Greets, > > > > Christian > > > > -- > > GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...) > > jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel > +++ > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...) jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
