Hello Andre
>>> TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING >>> 5356 >>> >>> [tomcat6.exe] >>> >>> >> Apart from the above and the other ports in LISTEN state, when "tomcat >> freezes", do you have any other ports in the netstat listing, shown as >> "CLOSE_WAIT" for example ? >> If yes, how many ? >> > These are the ports in the close wait state - TCP 127.0.0.1:3450 127.0.0.1:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 127.0.0.1:5152 127.0.0.1:1054 CLOSE_WAIT 2284 [jqs.exe] TCP 192.168.103.117:1790 184.84.255.35:80 <http://184.84.255.35/> CLOSE_WAIT 6008 [jucheck.exe] TCP 192.168.103.117:1973 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:2074 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:3825 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:4697 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:4701 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:4702 192.168.103.117:8080 CLOSE_WAIT 1836 [httpd.exe] TCP 192.168.103.117:4903 72.247.219.72:80 <http://72.247.219.72/> CLOSE_WAIT 2300 [jucheck.exe] >> Then, the next time Tomcat appears to freeze, try with a browser to access > the "freeze" page, as : > http://(hostname)/freeze/freeze.html > and as > http://(hostname):8080/freeze/freeze.html > > and let's see what happens. We have another test application running on tomcat, which also fails to respond once tomcat starts ignoring requests; so is the case with tomcat manager too. We are trying to replicate this behavior again by directly running tomcat on 80; will be posting the observations here. Thanks and Regards Sreekumar > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
