Martin Spinassi schrieb: > I've been trying to implement apache2 + connectors + tomcat on our > servers, put keep having disconnections from connectors and tomcat. > > Here I post some output from jk_mod_log: > > own, stopped or network problems (errno=110) > [Fri Nov 07 16:32:18.585 2008] [31998:670424352] [error] > ajp_get_reply::jk_ajp_common.c (1884): (worker1) Timeout with waiting > reply from tomcat. Tomcat is down, stopped or network problems > (errno=110) > [Fri Nov 07 16:32:18.710 2008] [31982:670424352] [info] > ajp_service::jk_ajp_common.c (2407): (worker1) sending request to tomcat > failed (recoverable), because of reply timeout (attempt=1) > [Fri Nov 07 16:32:18.710 2008] [31982:670424352] [error] > ajp_service::jk_ajp_common.c (2426): (worker1) connecting to tomcat > failed. > [Fri Nov 07 16:32:18.710 2008] [31982:670424352] [info] > jk_handler::mod_jk.c (2476): Service error=-10 for worker=worker1 > [Fri Nov 07 16:32:18.743 2008] [32102:670424352] [info] > ajp_service::jk_ajp_common.c (2407): (worker1) sending request to tomcat > failed (recoverable), because of reply timeout (attempt=1) > [Fri Nov 07 16:32:18.743 2008] [32102:670424352] [error] > ajp_service::jk_ajp_common.c (2426): (worker1) connecting to tomcat > failed. > > > > And makes tomcat stops responding. > > > Tomcat and apache are in the same machine, and they communicate each > other with loopback, so net problems are not an issue. > > > May be too many connections are made from apache to tomcat? Can I > configure max connections for a worker? > > > If I stop apache and make tomcat listen on port 80, it works smoothly > (even duplicating connections with jmeter!).
Give us your versions and configurations. We can't tell otherwise. You might also look at http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html and especially use connect_timeout and prepost_timeout. If the error message then is still "waiting reply", then you most likely have a problem in your application, namely things taking to long. Add a Tomcat access log valve with a custom pattern including %D to log the actual response times and check whether the are huge for some URLs. Look at those URLs and try to guess, why those are slow. You could also use Java Thread Dumps to inspect, what Tomcat (more precisely: your webapp) is actually doing. 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]
