Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 13743 invoked from network); 2 Dec 2002 21:10:32 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Dec 2002 21:10:32 -0000 Received: (qmail 28528 invoked by uid 97); 2 Dec 2002 21:11:34 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 28512 invoked by uid 97); 2 Dec 2002 21:11:33 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 28500 invoked by uid 98); 2 Dec 2002 21:11:33 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3DEBCCD1.4070906@carl.org> Date: Mon, 02 Dec 2002 14:12:49 -0700 From: eric scroger User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: Error? org/apache/ajp/tomcat4/Ajp13Connector createProcessor() References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thanks. I figured it was a bug. Unless anyone has any other information to the contrary, I'm going to file a bug report today. Seeing the Ajp package is deprecated, are the Warp connectors fairly stable? The documentation for the Warp connectors is weak (FIXME's) and incomplete when compared to the Ajp documentation. Eric Kevin Seguin wrote: >seems like a bug. > >either way, I believe the org.apache.ajp package is deprecated. > > > >>-----Original Message----- >>From: eric scroger [mailto:escroger@carl.org] >>Sent: Monday, December 02, 2002 12:40 PM >>To: Tomcat Developers List >>Subject: Error? org/apache/ajp/tomcat4/Ajp13Connector >>createProcessor() >> >> >>Greetings, >> >>We were noticing some 'No processor available' exceptions >>associated with the Ajp13Connectors under heavy load. >>I downloaded the Tomcat 4.0.6 connectors source and had >>a look at the code responsible for creating a new processor to >>handle an incoming Ajp13 socket connection from Apache. >> >>In org.apache.ajp.tomcat4.Ajp13Connector.java, in the >>createProcessor() method, I noticed that there was no logic >>to handle the case if maxProcessors was configured to "-1" >>for infinite processors. In the HttpConnector source, if >>maxProcessors was "-1", then it returned a newProcessor(). >>I modified this createProcessor() method to function in the >>same manner and the Ajp13 "No processor available" >>exceptions disappeared. >> >> private Ajp13Processor createProcessor() { >> >> synchronized (processors) { >> if (processors.size() > 0) >> return ((Ajp13Processor) processors.pop()); >> if ((maxProcessors > 0) && (curProcessors < maxProcessors)) >> return (newProcessor()); >> else { >> if ((maxProcessors < 0)) // my new code >>returns a new >>processor >> return (newProcessor()); // if maxProcessors >>is "-1", >>aka infinite. >> else return (null); >> >>// original else return result >> } >> } >>} >> >>My question then, is this a bug in the Ajp13Connector functionality? >>Or is there some design reason to not allow the user to configure >>the Ajp13Connector for infinite processors via the "-1" option. >>I couldn't locate any documentation that says Ajp13 connectors >>cannot and should not be configured for infinite processors. >> >>Thanks, >> >>Eric Scroger >> >> >> >> >> >>-- >>To unsubscribe, e-mail: >> unsubscribe@jakarta.apache.org> >>For >>additional commands, >>e-mail: >> >> >> >> > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: > > > -- To unsubscribe, e-mail: For additional commands, e-mail: