Hi Darin,
darinpope schrieb:
With this release, we were adding in some timeouts based on the
recommendations from
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
Previously, our workers.properties looked like:
worker.template-worker.type=ajp13
worker.template-worker.lbfactor=1
worker.810ED18641A24B1784CF0575992D73C7.reference=worker.template-worker
worker.810ED18641A24B1784CF0575992D73C7.host=192.168.1.100
worker.810ED18641A24B1784CF0575992D73C7.port=8209
and the AJP connector:
<Connector port="8209" enableLookups="false" protocol="AJP/1.3"
maxThreads="1000" />
What was happening is sometimes we would have some Tomcat threads "hung"
(never finished processing) and the Apache connections never released,
causing our site to stop responding. That's why I first put in the AJP
connectionTimeout. Then I started tweaking the workers.properties setting
based on the Timeout HOWTO.
If those are not necessary or if I'm tuning incorrectly for Windows, can you
give me some better settings to try?
For me there's nothing wrong with your configuration, apart from maybe
the 1000 threads. If you are using 32Bit Win, then it's likely, that you
will only be able to produce something between 400 and 500 threads.
What about reproducability of the error?
The one parameter I'm having least experience with, is socket_timeout.
Do you still get the error, if you do not use socket_timeout and lower
your thread number to 380?
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
