There's no configuration parameter for this -- it would take a code change in the code that listens on the server socket to pause for some amount of time if we've already allocated maxProcessors and all of them are currently busy.
I haven't looked at the code, but it doesn't sound like this should be too difficult to implement. Best bet is to submit an enhancement request: http://nagoya.apache.org/bugzilla/ For extra credit (and a *much* higher likelihood that it would get implemented quickly), a patch that makes it happen could be added as an attachment. Craig On Thu, 27 Feb 2003, Sankaranarayanan (Ganesh) Ganapathy wrote: > Date: Thu, 27 Feb 2003 13:58:31 -0800 > From: "Sankaranarayanan (Ganesh) Ganapathy" <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: RE: [BULK] - RE: [BULK] - Re: No processor available > > Ben, > > Thanx for pointing out. But I think that the documentation for the accept count > property is incorrect. > > In tomcat there is a thread that listens on the server socket and dispatches > connections on the server socket to one of the processors. When all the processors > are busy servicing earlier requests I think the server socket thread would still > pick up connections and then ultimately reject it since none of the processor are > available. The accept count as I understand merely determines how many incoming > connections will be accepted on the server socket - but it doesnt stop the server > socket thread from retrieving and attempting to dispatch these connections when all > the processors are busy. > > Is my understanding wrong? Can any of the gurus shed some light here. > > Thanx > Ganesh > > -----Original Message----- > From: Ben Ricker [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 27, 2003 11:54 AM > To: Tomcat Users List > Subject: [BULK] - RE: [BULK] - Re: No processor available > > > On Thu, 2003-02-27 at 13:37, Sankaranarayanan (Ganesh) Ganapathy wrote: > > How does the accept count property affect this? The accept count property merely > > determines the number of connections that will be queued on the socked. I am > > talking about a case where the connection is accepted from server socket but there > > is no processor available to process the request. > > Thanx > > Ganesh > > The following information is taken from Tomcat's 4.1.18 documentation. > If you have the documentation installed somewhere, the URL is: > > http://localhost/tomcat-docs/config/jk.html > > "acceptCount: > > The maximum queue length for incoming connection requests when all > possible request processing threads are in use. Any requests received > when the queue is full will be refused. The default value is 10." > > If I understand you, this is exactly what you are looking for? > > Ben Ricker > > > -----Original Message----- > > From: Ben Ricker [mailto:[EMAIL PROTECTED] > > Sent: Thursday, February 27, 2003 11:07 AM > > To: Tomcat Users List > > Subject: [BULK] - Re: No processor available > > > > > > On Thu, 2003-02-27 at 12:53, Sankaranarayanan (Ganesh) Ganapathy wrote: > > > Hi All, > > > > > > Currently I see that tomcat rejects requests with the message "No processor > > > available" if it has reached the maximum number of processors and the processors > > > are busy processing requests. > > > > > > Is there a way to make tomcat wait until a processor becomes available? > > > > > > Thanx > > > Ganesh > > > > Change the "Accept Count" property in the server.xml in the connector > > properties. > > > > > > Ben Ricker > -- > Ben Ricker <[EMAIL PROTECTED]> > Wellinx.com > > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
