I have a commercial app running Tomcat 6. I don't really know anything
about Tomcat, so I need some help with performance tuning.
What happens is that a small percentage of connections from our client
machines just timeout on the connect. I assume I'm running into some
limitation in Tomcat.
Pid pid at pidster.com writes:
Not really. Did you change the connectionTimeout downwards from the
default 60 secs to 3 secs?
Yes. Although the original version of the file was 20 seconds.
The clients (which I wrote) all have a 3 second connect timeout, so it seemed
to make sense to make
Caldarale, Charles R Chuck.Caldarale at unisys.com writes:
You keep contradicting yourself: is it a massive box, or can it
only support a miniscule number of threads?
Pick one.
Where did I say it could only support a miniscule number of threads?
I'm sorry if I accidentally gave that
Pid pid at pidster.com writes:
The basic point we're making is that you are twiddling the wrong knobs.
OK, good to know.
If you want to handle more connections, increase the size of the thread
pool that handles requests, don't increase the size of the queue of
requests waiting to be handled.
Caldarale, Charles R Chuck.Caldarale at unisys.com writes:
Using JConsole or VisualVM would be a good start.
OK, I'll take a look at those.
There's only one app running on this tomcat, if that makes
any difference.
Does it connect to a database (or any other external resource)?
If
I know absolutely nothing about tomcat but my company has just purchased
a product that uses it, and lucky me, I get to install it!
I set up a brand new Amazon Linux box (basically CentOS with some Amazon
enhancements). I installed tomcat6 and tomcat6-admin-webapps from yum.
Going to
Caldarale, Charles R Chuck.Caldarale at unisys.com writes:
Bad choice. Remove those, then download and install a real Tomcat 7
from tomcat.apache.org. The
third-party repackaged versions of Tomcat garble so much that it's
very difficult to provide any kind of
support info for them.
I
