hello, i have a similar (the same?) problem, where i currently do not know what's really the root cause of it.
i was monitoring my webapp (apache 2.0.52, tomcat 5.0.28, mod_jk2, later tomcat 5.5.7 with mod_jk 1.2.8) on port 80 (apache/mod_jk) by requesting a given url with curl. sometimes the url was not reachable, the output of curl then was "curl: (6) name lookup timed out". the netstat-output was sometimes ok (cons in state ESTABLISHED), but sometimes it looked like the following: > tcp 1 0 127.0.0.1:50195 127.0.0.1:8009 > CLOSE_WAIT 12109/httpd > tcp 1 0 127.0.0.1:50203 127.0.0.1:8009 > CLOSE_WAIT 12113/httpd > tcp 1 0 127.0.0.1:50228 127.0.0.1:8009 > CLOSE_WAIT 12108/httpd > tcp 1 0 127.0.0.1:50215 127.0.0.1:8009 > CLOSE_WAIT 12111/httpd > tcp 0 0 127.0.0.1:50258 127.0.0.1:8009 > ESTABLISHED 12112/httpd > tcp 0 0 127.0.0.1:50262 127.0.0.1:8009 > ESTABLISHED 3268/httpd > tcp 0 0 127.0.0.1:50240 127.0.0.1:8009 > ESTABLISHED 12110/httpd > tcp 0 0 127.0.0.1:50244 127.0.0.1:8009 > ESTABLISHED 13759/httpd > tcp 0 0 127.0.0.1:50249 127.0.0.1:8009 > ESTABLISHED 12114/httpd > tcp 0 0 127.0.0.1:50254 127.0.0.1:8009 > ESTABLISHED 12115/httpd > tcp 0 0 ::ffff:127.0.0.1:50238 ::ffff:127.0.0.1:3306 > ESTABLISHED 12562/java > tcp 0 0 ::ffff:127.0.0.1:50237 ::ffff:127.0.0.1:3306 > ESTABLISHED 12562/java > tcp 0 0 ::ffff:127.0.0.1:8009 ::ffff:127.0.0.1:50262 > ESTABLISHED 12562/java > tcp 0 0 ::ffff:127.0.0.1:8009 ::ffff:127.0.0.1:50258 > ESTABLISHED 12562/java > tcp 0 0 ::ffff:127.0.0.1:8009 ::ffff:127.0.0.1:50254 > ESTABLISHED 12562/java > tcp 0 0 ::ffff:127.0.0.1:8009 ::ffff:127.0.0.1:50249 > ESTABLISHED 12562/java > tcp 0 0 ::ffff:127.0.0.1:8009 ::ffff:127.0.0.1:50244 > ESTABLISHED 12562/java > tcp 0 0 ::ffff:127.0.0.1:8009 ::ffff:127.0.0.1:50240 > ESTABLISHED 12562/java then i added the hostname of the requested url to /etc/hosts, and since then everything was ok. adding the hostname to /etc/hosts was my last action, after that i was not further debugging. my environment: 2.6.10-1.760_FC3 tomcat5-5.5.7-2jpp httpd-2.0.52-3.1 mod_jk-ap20-1.2.8-1jpp cheers, martin On Fri, 2005-02-18 at 15:49 +0100, Michael Stiller wrote: > Hi, > > i have the following problem with mod_jk from tomcat-connectors (1.2.5 - > 1.2.8) including 1.2.9 (from cvs). > > Environment: > apache is 2.0.52, forking model, server os is linux 2.6.10-1.760_FC3smp > (fedora core 3), mod_jk 1.2.9 (others tested as well) > > After a while i get sockets stuck in CLOSE_WAIT state and netstat shows > 1 byte in the receive queue for this socket. > > tcpdump shows, that the backend (jetty) half-closes the connection with > FIN. That FIN is acked from the mod_jk machine but the connection is not > closed (no FIN is send). > > sample netstat output: > ... > tcp 1 0 192.168.100.1:51003 192.168.170.8:32511 > CLOSE_WAIT > tcp 1 0 192.168.100.1:53875 192.168.170.8:12522 > CLOSE_WAIT > tcp 1 0 192.168.100.1:53619 192.168.170.8:12521 > CLOSE_WAIT > ... > > Are there any known issues? Where do is start debugging this? What information > is missing? > > TIA, > > Michael > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Martin Grotzke Hohenesch 38, 22765 Hamburg Tel. +49 (0) 40.39905668 Mobil +49 (0) 170.9365656 E-Mail [EMAIL PROTECTED] Online http://www.javakaffee.de
signature.asc
Description: This is a digitally signed message part
