On 05.09.2009 11:02, Joseph2009 wrote: > > I am using Tomcat 5.5.20 and Apache 2.2 with Mod_jk 1.2.2.7 on Solaris 10 > intel platform. Following is my configurations > > Tomcat > > port="8030" > enableLookups="false" > redirectPort="8444" > protocol="AJP/1.3" > compression="on" > compressableMimeType="text/html,text/xml,text/css,text/javascript" > maxThreads="250" > maxSpareThreads="75" > minSpareThreads="25" > connectionTimeout="600000" > > Apache > > <IfModule mpm_prefork_module> > StartServers 10 > MinSpareServers 10 > MaxSpareServers 20 > MaxClients 200 > MaxRequestsPerChild 0 > </IfModule> > > mod_jk > worker.template.type=ajp13 > worker.template.lbfactor=1 > worker.template.ping_timeout=1000 > worker.template.ping_mode=A > worker.template.socket_timeout=10 > worker.template.connection_pool_timeout=600 > worker.anznz.reference=worker.template > worker.anznz.host=localhost > worker.anznz.port=8030 > > My website is running fine for the entire day and mod_jk started throwing > the following error end of the day > > [Sat Sep 05 11:27:05 2009][23566:1] [error] jk_ajp_common.c (2400): (xxxx) > sending request to tomcat failed (unrecoverable), (attempt=1) > > [Sat Sep 05 11:27:04 2009][7724:1] [info] jk_ajp_common.c (1104): (xxxx) > can't receive the response message from tomcat, tomcat (127.0.0.1:8030) has > forceda connection close for socket 36 > > [Sat Sep 05 11:27:05 2009][7724:1] [error] jk_ajp_common.c (1920): (xxxx) > Tomcat is down or refused connection. No response has been sent to the > client (yet > ) > > Once the abouve error hits, the user get the service not available pages. It > is not happening to all users. Then when I restart the Tomcat, it started > working. There is no problem in accessing the site through the HTTP > connector in the Tomcat. > > Did someone experience similar problem and is there any solution for this > problem?
Maybe you run out of Tomcat threads because requests start hanging and slowly your thread pool gets exhausted. Try to do a few (like 3) thread dumps, each a few (like 3) seconds apart form each other. Thread Dump: kill -QUIT to the Tomcat PID. It writes a list of all thread to catalina.out, together with their stack, i.e. what code they are running at that moment). Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
