Mr. Turk
> 1. connectionTimeout will cause the socket to be closed after 20s
> if no AJP requests come in within that time.
> So you will have those [info] messages.
the [info] messages reduced by increasing the value of connectionTimeout.
Thank you so much!
I'm going to try to change the value to make it more appropriately.
Best regards,
(2011/02/17 17:01), Mladen Turk wrote:
On 02/17/2011 04:26 AM, Yu Kikuchi wrote:
[httpd.conf](preforkMPM)
worker.worker01.connection_pool_timeout=20
No need for that if running prefork mpm.
<Connector protocol="AJP/1.3" port="8009" address="${jboss.bind.address}"
maxThreads="81" connectionTimeout="20000" redirectPort="8443" allowTrace="false"
/>
1. connectionTimeout will cause the socket to be closed after 20s
if no AJP requests come in within that time.
So you will have those [info] messages.
Since you have MaxClients and maxThreads in sync you can
set connectionTimeout="-1".
The only problem might arise if you do a graceful restart on
httpd with active connections in which case httpd will spawn
couple of extra connections for new requests.
So set connectionTimeout="600000" (10 minutes) and just
live with those [info] messages, or
MaxClients 81, maxThreads="100" and connectionTimeout="-1"
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
