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]
