The focus should be on the tomcat tweaking. We get errors in the tomcat error logs that say tomcat has reached its connection limits. I never said that it was serving slow. It hits connection limits which means that the app will not serve any more traffic until connections clear.
If a box definitely has more capacity (dual core, dual procs), then my best guess is that tomcat is not tuned perfectly to allow the max amount of connections in. We have raised MaxThreads in the past to allow more connections in. This works, but surely other knobs are important to be tweaked. I am looking for good definitions and/or best practices on which knobs to tweak to allow the max connections in before exhausting the jvm native memory allocation or cpu on the box. Thanks, J On 2/15/07, Andrew Miehs <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear J' What do you mean you are hitting connection limits?! Are you getting errors? What are you seeing that makes you think that is slow? Is there a database involved in this application? I assume you are running linux on your server, with a 2.6 kernel. run the following commands while your box 1) ps auxH 2) ps auxH |grep -c java 3) vmstat 5 5 4) iostat 5 3 Then we will have a bit of an idea what is going on. Andrew On 15/02/2007, at 9:36 PM, j r wrote: > The reason it is hitting its limits is easy: traffic. We easily > get enough > website traffic to overflow the connection limits unless I have > many boxes > available to serve. I know these can be configured to handle more > connections. I know that we should be able to do this in the tomcat > server. That is why I need those tweaking parameters defined. > > > > Thanks, > j > > On 2/15/07, Leon Rosenberg <[EMAIL PROTECTED]> wrote: >> >> First you should investigate why tomcat is hitting its limits. >> Why do you think it does? Which resource is the limit? >> Do you have/use any monitoring software? moskito? lambdaprobe? >> tomcat-manager? >> >> regards >> Leon >> >> On 2/15/07, j r <[EMAIL PROTECTED]> wrote: >> > I have searched for exact documentation on this, and I always find >> > conflicting info. Therefore I am reaching out to this list. I >> have the >> > following info and questions: >> > >> > - we are running tomcat 5.5.20 >> > - we have the following configs in server.xml: >> > <Connector port="8009" >> > enableLookups="false" redirectPort="8443" debug="0" >> > maxThreads="750" minSpareThreads="100" >> maxSpareThreads="250" >> > acceptCount="100" connectionTimeout="5000" >> > tomcatAuthentication=" >> > false" >> > >> > - we have extra capacity (mem, cpu, etc.) on the servers, yet >> tomcat is >> > hitting connection limits >> > - we feel that tomcat can serve more, so what do we tune to make >> it do >> so? >> > - maxThreads? >> > - minSpareThreads? >> > - maxSpareThreads? >> > - acceptCount? >> > >> > >> > Honestly, I would rather love an exact definition of what each >> of those >> > would do to the tomcat server if tweaked. Knowing that would be >> nirvana >> for >> > tuning. >> > >> > >> > >> > -j >> > >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFF1NaFW126qUNSzvURAuxZAJ4ugkLObXKHJZsSIfX3SWzZzv5vlQCdHXeV jSPVOQqZXoxvlQc7Q94vMlA= =YSSz -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
