On 10/23/2012 12:01 PM, Charles Richard wrote:
Hi,
I am doing load testing. I'm trying to ensure that our production site can
handle as much traffic as it possibly can and I'm trying to make sure I
refine my performance tuning skills on a test environment. Here are some
more specifics:
Mod_jk is 1.2.31
Settings in workers.properties:
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8009
worker.worker1.connection_pool_timeout=180
worker.worker1.lbfactor=1
A quick note here on your AJP workers.properties
the worker.worker1.connection_pool_timeout (in seconds) should match the
connectionTimeout (in milliseconds) attribute for your AJP Connector
element in server.xml. By default, the connectionTimeout is infinite (no
timeout).
In recent versions of the AJP connector, there is a sample
workers.properties file in the conf directory. There are a lot of good
comments in that file.
The latest version is 1.2.37, and you might investigate using that.
Read the following changelog for information:
http://tomcat.apache.org/connectors-doc/miscellaneous/changelog.html
I'm not sure how many threads would be good to handle how many connections
:) I'm just trying to understand more of the process so i can start
fine-tuning where I can. Right now, I'm trying to understand why Tomcat
could not respond anymore if threads are still waiting but maybe with the
server being cpu bound as it is, it's just taking a long long time and
everything is as could be "expected".
Cheers,
Charles
On Tue, Oct 23, 2012 at 3:50 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Charles,
On 10/23/12 10:45 AM, Charles Richard wrote:
I'm testing performance of our Java application in Tomcat (6.0.30)
and we have maxThreads set to 750. I noticed that when i did a
netstat -an | grep my_ajp_port, i saw around 860 connections.
In what TCP state were they? If you are doing load-testing, you might
see a lot in TIME_WAIT or TIME_WAIT2 as they (slowly) shutdown.
What is your connector configuration? Be specific.
Wanting to know what was happening, I did a jstack of my tomcat pid
and inspected the track with Samurai.
I was expecting to see > 750 Worker Threads in my stack since some
extra worker threads are needed by Tomcat. What i saw was around
60 worker threads in the trace.
Sounds great: Tomcat can handle your 750 connections with only 60
threads. Sounds good, no?
- -chris
. . . . just my two cents
/mde/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
