Hi, The application does not make database connection. Instead makes and http request to web server to fetch content.
This web server is heavily loaded with traffic. The high end web server configuration and optimization handles all the request quite efficiently. (No doubt on the web server processing speed) Thanks and Regards, -Prashant Thakkar. On 6/19/07, Brantley Hobbs <[EMAIL PROTECTED]> wrote:
Prashant, Unless I'm load-testing, the only time I've seen thread counts that high is when something is wrong with the app, and it's usually a database connection that hasn't been closed. Check the number of database connections in use out of the pool (this is typically something that you'd do on the database server itself; I don't know of any mechanism in Tomcat to get that measurement). If that is also an extraordinarily large number, then you might consider checking for database connections that haven't been closed. For typical sites, you really don't usually need a database connection pool any larger than a few tens of connections. What happens is that the database connection pool (or the database server itself) exhausts its supply of connections, and new requests that come in to Tomcat queue until more connections come open or the connection requests time out. Good luck. B. Prashant Thakkar wrote: > Hi, > > Thanks, > But this is the clients application which we are running. We dont have > the > access to the servlet code. That was the the obvious reason we had > increased > the thread limit to 250. > > Other thing i would like to know is about the thread pooling. How can > i use > this with tomcat 5.0.28 > Below is the connector which we are using: > > <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --> > <Connector port="8080" > maxThreads="250" minSpareThreads="25" maxSpareThreads="75" > enableLookups="false" redirectPort="8443" acceptCount="100" > debug="0" connectionTimeout="0" > disableUploadTimeout="true" /> > <!-- Note : To disable connection timeouts, set connectionTimeout value > to 0 --> > > <!-- Note : To use gzip compression you could set the following > properties : > > compression="on" > compressionMinSize="2048" > noCompressionUserAgents="gozilla, traviata" > compressableMimeType="text/html,text/xml" > --> > > <!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 --> > <!-- > <Connector port="8443" > maxThreads="150" minSpareThreads="25" maxSpareThreads="75" > enableLookups="false" disableUploadTimeout="true" > acceptCount="100" debug="0" scheme="https" secure="true" > clientAuth="false" sslProtocol="TLS" /> > --> > > <!-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 --> > <Connector port="8009" > enableLookups="false" redirectPort="8443" debug="0" > protocol="AJP/1.3" /> > > <!-- Define a Proxied HTTP/1.1 Connector on port 8082 --> > <!-- See proxy documentation for more information about using this. --> > <!-- > <Connector port="8082" > maxThreads="150" minSpareThreads="25" maxSpareThreads="75" > enableLookups="false" > acceptCount="100" debug="0" connectionTimeout="20000" > proxyPort="80" disableUploadTimeout="true" /> > --> > > Thanks and Regards, > - Prashant Thakkar > > On 6/19/07, Robert Harper <[EMAIL PROTECTED]> wrote: >> >> Do as it says and increase the max threads parameter or manage your >> threads >> better. >> >> Robert S. Harper >> Senior Engineer >> Information Access Technology, Inc. >> 1100 East 6600 South, Suite 300 >> Salt Lake City Utah USA 84121-7411 >> (801)265-8800 Ext. 255 >> FAX (801)265-8880 >> >> >> This e-mail is intended only for the addressee and may contain >> confidential >> and/or privileged information. Any review, retransmission, or action >> taken >> upon this information by persons other than the intended recipient is >> prohibited by law. If you received this communication in error, please >> contact us immediately at 801-265-8800. Although this e-mail and any >> attachments are believed to be free of any virus or other defect, it is >> the >> responsibility of the recipient to ensure that anything received or >> opened >> is virus free. No responsibility is accepted by IAT for any loss or >> damage >> in the event that such a virus or defect exists. >> >> -----Original Message----- >> From: Prashant Thakkar [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, June 19, 2007 7:25 AM >> To: users@tomcat.apache.org >> Subject: How can i configure tomcat to avoid threads error in tomcat >> >> Hi All, >> >> I am frequently getting this error in tomcat which stops my tomcat >> service. >> Pl help me its urgent and costing my service as well: >> >> I am getting bellow error in my catalina logs: >> Jun 19, 2007 5:55:44 PM org.apache.tomcat.util.threads.ThreadPool >> logFull >> SEVERE: All threads (250) are currently busy, waiting. Increase >> maxThreads >> (250) or check the servlet status >> Thanks in advance >> - Prashant Thakkar >> >> >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Prashant Thakkar
