Hello Mladen, Thursday, December 22, 2005, 8:43:42 AM, you wrote: MT> Grzegorz Tańczyk wrote: >> Hello >> >> My configuration is: >> - single machine with Slackware 10 >> - apache 2.0.55 with worker MPM >> - tomcat 5.5.4 >> - mod_jk 1.2.15 >> >> Here is my apache<->tomcat configuration >> >> [user]->[mydomain.com vhost]-ProxyPass->[localhost vhost]-JKMount->[Tomcat] MT> Perhaps posting workers.properties would help. worker.w1.type=ajp13 worker.w1.host=localhost worker.w1.port=8000 worker.w1.cachesize=200 worker.w1.cache_timeout=300 worker.w1.socket_timeout=300 worker.w1.socket_keepalive=0 worker.w1.recycle_timeout=100 worker.w1.recovery_options=3 worker.w1.prepost_timeout=100000 worker.w1.connect_timeout=100000 worker.w1.reply_timeout=100000
Other w2 and w3 have cachesize 100. cache_timeout unit is second or milisecond? And also there is a ProxyTimeout(20 seconds) before first ProxyPass. >> Everything works almost fine, but in some unknown circumstances I >> see in apache status that all workers(1000) are busy in R or W >> state. MT> Did you set the cachesize for workers? MT> Here is a simple math: MT> (MaxClients/ThreadsPerChild)*cachesize=maxThreads MT> You might also add retries=60 to the worker. More retries = longer connection and more httpd workers busy? What is the diffrence between AJP and HTTP connector in threads management? Why AJP doesn't keep idle threads in (R)eady stage When I disable connectionTimeout then after few moments tomcat hangs(all threads are in (K)eepalive stage, but when I enable connectionTimeout then all threads are killed after connection is finished or timed out. Isn't it lost of time to create new threads for each new connection? Thanks for reply. MT> Regards, MT> Mladen. -- Best regards, Grzegorz mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
