Tomcat 6 does not respond or freeze after startup
Hello, I have some problems to get my Tomcat running. I have installed a fresh zip version of Tomcat 6.0.29 on my WinXP SP3 PC with Java 1.6.0_20 running a non admin account. The startup is successfull following the logs. But after the first access to http://localhost:8080 Tomcat stops responding. It doesn't show the homepage again nor respond to any links. I have configured tomcat for Log4j with DEBUG level. There I could see that the Tomcat is still refreshing its contexts. See tomcat.log below [1]. To identify if there are any memory problems I tried to check with VisualVM. It takes quite a long time (2+ minute) to connect to the tomcat jvm instance. But Heap space (12MB) is only use 30% and PermGen (16MB) only 50%. VisualVM states 43 active live threads (42 demon threads). See thread dump below [2]. Do you have any ideas why my Tomcat isn't responding? What else could I check to identify the problem? Thank you and kind regards, T. Gau [1] tomcat.log EBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1280782997390 sessioncount 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1280782997390 sessioncount 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1280782997390 sessioncount 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1280782997390 sessioncount 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - Start expire sessions StandardManager at 1280782997390 sessioncount 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.session.ManagerBase - End expire sessions StandardManager processingTime 0 expired sessions: 0 DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[] redeploy resource D:\Entwicklung\apache-tomcat-6.0.29\webapps\ROOT DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[] reload resource D:\Entwicklung\apache-tomcat-6.0.29\conf\context.xml DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[] reload resource D:\Entwicklung\apache-tomcat-6.0.29\webapps\ROOT\WEB-INF\web.xml DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[] reload resource D:\Entwicklung\apache-tomcat-6.0.29\conf\web.xml DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[/manager] redeploy resource D:\Entwicklung\apache-tomcat-6.0.29\webapps\manager DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[/manager] redeploy resource D:\Entwicklung\apache-tomcat-6.0.29\conf\Catalina\localhost\manager.xml DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[/manager] reload resource D:\Entwicklung\apache-tomcat-6.0.29\conf\Catalina\localhost\manager.xml DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[/manager] reload resource D:\Entwicklung\apache-tomcat-6.0.29\conf\context.xml DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[/manager] reload resource D:\Entwicklung\apache-tomcat-6.0.29\conf\web.xml DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[/manager] reload resource D:\Entwicklung\apache-tomcat-6.0.29\webapps\manager\WEB-INF\web.xml DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] org.apache.catalina.startup.HostConfig - Checking context[/docs] redeploy resource D:\Entwicklung\apache-tomcat-6.0.29\webapps\
Re: Tomcat 6 does not respond or freeze after startup
Hello, thank you for your response. @Version: I have downloaded the following Tomcat version: http://ftp.fernuni-hagen.de/ftp-dir/pub/mirrors/www.apache.org/tomcat/tomcat-6/v6.0.29/bin/apache-tomcat-6.0.29-windows-x86.zip @Logs: localhost.2010-08-03.log 03.08.2010 21:33:42 org.apache.catalina.core.ApplicationContext log INFO: ContextListener: contextInitialized() 03.08.2010 21:33:42 org.apache.catalina.core.ApplicationContext log INFO: SessionListener: contextInitialized() manager.2010-08-03.log catalina.2010-08-03.log 03.08.2010 21:33:41 org.apache.catalina.core.AprLifecycleListener init INFO: Loaded APR based Apache Tomcat Native library 1.1.20. 03.08.2010 21:33:41 org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. 03.08.2010 21:33:42 org.apache.coyote.http11.Http11AprProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 03.08.2010 21:33:42 org.apache.coyote.ajp.AjpAprProtocol init INFO: Initializing Coyote AJP/1.3 on ajp-8009 03.08.2010 21:33:42 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 574 ms 03.08.2010 21:33:42 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 03.08.2010 21:33:42 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.29 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory docs 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory examples 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory host-manager 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory manager 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory ROOT 03.08.2010 21:33:42 org.apache.coyote.http11.Http11AprProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 03.08.2010 21:33:42 org.apache.coyote.ajp.AjpAprProtocol start INFO: Starting Coyote AJP/1.3 on ajp-8009 03.08.2010 21:33:42 org.apache.catalina.startup.Catalina start INFO: Server startup in 318 ms host-manager.2010-08-03.log That is all logging which takes place until Tomcat freezes. After that there are no more updates on the logs. Kind regards, T. Gau Mark Thomas schrieb am 02.08.2010 23:39: On 02/08/2010 22:29, T. Gau wrote: Hello, I have some problems to get my Tomcat running. I have installed a fresh zip version of Tomcat 6.0.29 on my WinXP SP3 PC with Java 1.6.0_20 running a non admin account. Which zip? There are several. The startup is successfull following the logs. But after the first access to http://localhost:8080 Tomcat stops responding. It doesn't show the homepage again nor respond to any links. Could we see those logs please. I have configured tomcat for Log4j with DEBUG level. There I could see that the Tomcat is still refreshing its contexts. See tomcat.log below [1]. Don't do that. Just use a clean install with the default config. When that works, then start tweaking stuff. To identify if there are any memory problems I tried to check with VisualVM. It takes quite a long time (2+ minute) to connect to the tomcat jvm instance. But Heap space (12MB) is only use 30% and PermGen (16MB) only 50%. VisualVM states 43 active live threads (42 demon threads). See thread dump below [2]. If connections take that long there is something seriously wrong. Do you have any ideas why my Tomcat isn't responding? What else could I check to identify the problem? See above. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 does not respond or freeze after startup
Hello, I tried to connect via telnet without success: Microsoft Telnet> open localhost 8080 Verbindungsaufbau zu localhost... (Connecting to localhost ...) Verbindung zu Host verloren. (Connection to host lost.) Microsoft Telnet> While I could connect with a web browser at least once after startup, I never could get a connection with telnet. Kind regards, T. Gau Mark Thomas schrieb am 03.08.2010 22:00: On 03/08/2010 20:38, T. Gau wrote: Hello, thank you for your response. @Version: I have downloaded the following Tomcat version: http://ftp.fernuni-hagen.de/ftp-dir/pub/mirrors/www.apache.org/tomcat/tomcat-6/v6.0.29/bin/apache-tomcat-6.0.29-windows-x86.zip @Logs: localhost.2010-08-03.log 03.08.2010 21:33:42 org.apache.catalina.core.ApplicationContext log INFO: ContextListener: contextInitialized() 03.08.2010 21:33:42 org.apache.catalina.core.ApplicationContext log INFO: SessionListener: contextInitialized() manager.2010-08-03.log catalina.2010-08-03.log 03.08.2010 21:33:41 org.apache.catalina.core.AprLifecycleListener init INFO: Loaded APR based Apache Tomcat Native library 1.1.20. 03.08.2010 21:33:41 org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. 03.08.2010 21:33:42 org.apache.coyote.http11.Http11AprProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 03.08.2010 21:33:42 org.apache.coyote.ajp.AjpAprProtocol init INFO: Initializing Coyote AJP/1.3 on ajp-8009 03.08.2010 21:33:42 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 574 ms 03.08.2010 21:33:42 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 03.08.2010 21:33:42 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.29 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory docs 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory examples 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory host-manager 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory manager 03.08.2010 21:33:42 org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory ROOT 03.08.2010 21:33:42 org.apache.coyote.http11.Http11AprProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 03.08.2010 21:33:42 org.apache.coyote.ajp.AjpAprProtocol start INFO: Starting Coyote AJP/1.3 on ajp-8009 03.08.2010 21:33:42 org.apache.catalina.startup.Catalina start INFO: Server startup in 318 ms host-manager.2010-08-03.log That is all logging which takes place until Tomcat freezes. After that there are no more updates on the logs. That all looks normal. Maybe a firewall in the way. Try connecting to port 8080 via telnet. Makr - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 does not respond or freeze after startup
@Modified: I have not modified anything. Just unzipped Tomcat via 7zip and moved it to program folder. @ARP: Disabling ARP as described below doesn't help. Tomcat is still freezing, no access via telnet possible. @IPv6: As fas as I know, I'm not running IPv6. IPconfig doesn't show any IPv6 specific. Thanks and kind regards, T. Gau Caldarale, Charles R schrieb am 03.08.2010 23:27: From: T. Gau [mailto:t...@normad.de] Subject: Re: Tomcat 6 does not respond or freeze after startup I tried to connect via telnet without success: If you've changed _anything_ in server.xml, please post it, preferably with comments removed and privileged information masked. If you haven't changed it, just state that. Try disabling APR by renaming the tcnative-1.dll file in Tomcat's bin directory. This will get you the pure Java connector, so we can see if there's some problem with APR in your setup. (Your logs show it is currently being used.) Are you running IPv6-only by any chance? The JVM doesn't handle that well. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 does not respond or freeze after startup
Hello, my Windows Firewall is 'Inactive'. Instead I'm using the Ashampoo Firewall FREE. But I could not connect to Tomcat via telnet even if I stop this firewall, too. Kind regards, Tilo Caldarale, Charles R schrieb am 04.08.2010 00:06: From: T. Gau [mailto:t...@normad.de] Subject: Re: Tomcat 6 does not respond or freeze after startup @ARP: Disabling ARP as described below doesn't help. Tomcat is still freezing, no access via telnet possible. Then I have to think it's what Mark said: your Windows firewall is getting in the way. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 does not respond or freeze after startup
Hello, I have executed 'netstat -anopb tcp' with the following result: TCP0.0.0.0:8009 0.0.0.0:0 LISTENING 3436[java.exe] TCP0.0.0.0:8080 0.0.0.0:0 LISTENING 3436[java.exe] TCP127.0.0.1:8005 0.0.0.0:0 LISTENING 3436 [java.exe] I could not find another listening port for java.exe. BUT the requests to the frozen Tomcat results into TCP127.0.0.1:8080 127.0.0.1:2049 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2050 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1992 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1991 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2051 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1990 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1989 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2043 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2042 CLOSE_WAIT 3436[java.exe] Any ideas what happens here? Later this week I will try to setup a virtual machine running WinXP and Tomcat to check again. Kind regards, T.Gau Caldarale, Charles R schrieb am 04.08.2010 15:32: From: T. Gau [mailto:t...@normad.de] Subject: Re: Tomcat 6 does not respond or freeze after startup my Windows Firewall is 'Inactive'. Instead I'm using the Ashampoo Firewall FREE. But I could not connect to Tomcat via telnet even if I stop this firewall, too. With Tomcat running, what does "netstat -anop tcp" show? The Tomcat process should be listening on ports 8005, 8009, and 8080, as in the following: TCP 0.0.0.0:80090.0.0.0:0 LISTENING 4720 TCP 0.0.0.0:80800.0.0.0:0 LISTENING 4720 TCP 127.0.0.1:8005 0.0.0.0:0 LISTENING 4720 (There should also be one other port Tomcat is listening on, but its value varies.) If all of that looks normal, then I'd try running Tomcat on another machine, preferably one with a clean installation of Windows. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 does not respond or freeze after startup
Hello, I assumed that I'm not running IPv6 because ipconfig didn't show an IPv6 address. Any ideas how to play safe? Kind regards, T. Gau Christopher Schultz schrieb am 04.08.2010 15:54: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 T., On 8/3/2010 5:46 PM, T. Gau wrote: @IPv6: As fas as I know, I'm not running IPv6. IPconfig doesn't show any IPv6 specific. Sure? From your own log file: INFO: Loaded APR based Apache Tomcat Native library 1.1.20. 03.08.2010 21:33:41 org.apache.catalina.core.AprLifecycleListener init INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxZcREACgkQ9CaO5/Lv0PDATgCeJgblMBp8yvyNzRZHFxnf3KbK 6RMAmwctcSbfeOFYKVpvFEk3KzrB5onb =4/BI -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 does not respond or freeze after startup
Hello, the CLOSE_WAIT connections are persistent (waiting 10+min now). The FIN_WAIT counterparts from the browser disapear after some time. As a reminder: The Tomcat installation is "untouched". No configuration and no deployed applications besides these allready packaged with Tomcat. Kind regards, T. Gau André Warnier schrieb am 04.08.2010 23:11: Hi T. T. Gau wrote: Hello, I have executed 'netstat -anopb tcp' with the following result: TCP0.0.0.0:8009 0.0.0.0:0 LISTENING 3436[java.exe] TCP0.0.0.0:8080 0.0.0.0:0 LISTENING 3436[java.exe] TCP127.0.0.1:8005 0.0.0.0:0 LISTENING 3436 [java.exe] I could not find another listening port for java.exe. The above is perfectly normal and classical. It shows - a listening port 8080, for the HTTP Connector - a listening port 8009, for the AJP Connector - a listening port 8005, for the Tomcat shutdown connector BUT the requests to the frozen Tomcat results into TCP127.0.0.1:8080 127.0.0.1:2049 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2050 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1992 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1991 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2051 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1990 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1989 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2043 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2042 CLOSE_WAIT 3436[java.exe] Any ideas what happens here? That is more interesting. If the situation above is transitory (just lasts a few seconds), then it might be normal. If the situation above persists for a long tine, then it shows that Tomcat (or something within Tomcat) is not properly closing its end of client sockets, and that the objects containing these sockets are lingering on the Heap, waiting to be collected. I'm sure someone else on this list could suggest a scenario where a badly-behaved application could achieve this. (or a very large keepAlive setting ?) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 does not respond or freeze after startup
Check: No IPv6. Kind regards. Caldarale, Charles R schrieb am 04.08.2010 23:23: From: T. Gau [mailto:t...@normad.de] Subject: Re: Tomcat 6 does not respond or freeze after startup I assumed that I'm not running IPv6 because ipconfig didn't show an IPv6 address. Any ideas how to play safe? Look at the properties of each Network Connection and see if the "Microsoft TCP/IP version 6" box is checked. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 does not respond or freeze after startup
a.exe] TCP127.0.0.1:8080 127.0.0.1:1266 CLOSE_WAIT 2408[java.exe] After closing tomcat TCP127.0.0.1:1256 127.0.0.1:8080 FIN_WAIT_2 3568[System] TCP127.0.0.1:1257 127.0.0.1:8080 FIN_WAIT_2 3568[System] TCP127.0.0.1:8080 127.0.0.1:1267 CLOSE_WAIT 2408[java.exe] TCP127.0.0.1:8080 127.0.0.1:1257 CLOSE_WAIT 2408[java.exe] TCP127.0.0.1:8080 127.0.0.1:1265 CLOSE_WAIT 2408[java.exe] TCP127.0.0.1:8080 127.0.0.1:1256 CLOSE_WAIT 2408[java.exe] TCP127.0.0.1:8080 127.0.0.1:1268 CLOSE_WAIT 2408[java.exe] TCP127.0.0.1:8080 127.0.0.1:1264 CLOSE_WAIT 2408[java.exe] TCP127.0.0.1:8080 127.0.0.1:1263 CLOSE_WAIT 2408[java.exe] TCP127.0.0.1:8080 127.0.0.1:1262 CLOSE_WAIT 2408[java.exe] TCP127.0.0.1:8080 127.0.0.1:1266 CLOSE_WAIT 2408[java.exe] TCP127.0.0.1:8080 127.0.0.1:1261 CLOSE_WAIT 2408[java.exe] Later after some time System is closing its sockets, too. After the freeze of Tomcat the Firefox browser shows the "loading sign" for each request against http://localhost:8080. Hope this helps identifying the problem. Kind regards, T. Gau André Warnier schrieb am 05.08.2010 01:08: T. Gau wrote: Hello, the CLOSE_WAIT connections are persistent (waiting 10+min now). The FIN_WAIT counterparts from the browser disapear after some time. As a reminder: The Tomcat installation is "untouched". No configuration and no deployed applications besides these allready packaged with Tomcat. Ok. But from the netstat dislay below, it looks as if a number of processes *local to the server* and with PID's 2049,2050,1992,1991 etc.. /have/ connected to Tomcat on port 8080. What are these processes, and are they still alive when you take this netstat screenshot ? Can you briefly remind us of what kind of request to Tomcat these clients are issuing, and what happens in them while they wait/don't wait for a response ? (A long time ago, I got some "ps.exe" program - probably in a Windows/NT Toolkit - which is easier than the Task Manager to look this up and cut/paste. Apparently still available in some form : http://technet.microsoft.com/en-us/sysinternals/bb795532.aspx ) Kind regards, T. Gau André Warnier schrieb am 04.08.2010 23:11: Hi T. T. Gau wrote: Hello, I have executed 'netstat -anopb tcp' with the following result: TCP0.0.0.0:8009 0.0.0.0:0 LISTENING3436[java.exe] TCP0.0.0.0:8080 0.0.0.0:0 LISTENING3436[java.exe] TCP127.0.0.1:8005 0.0.0.0:0 LISTENING3436 [java.exe] I could not find another listening port for java.exe. The above is perfectly normal and classical. It shows - a listening port 8080, for the HTTP Connector - a listening port 8009, for the AJP Connector - a listening port 8005, for the Tomcat shutdown connector BUT the requests to the frozen Tomcat results into TCP127.0.0.1:8080 127.0.0.1:2049 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2050 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1992 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1991 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2051 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1990 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:1989 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2043 CLOSE_WAIT 3436[java.exe] TCP127.0.0.1:8080 127.0.0.1:2042 CLOSE_WAIT 3436[java.exe] Any ideas what happens here? That is more interesting. If the situation above is transitory (just lasts a few seconds), then it might be normal. If the situation above persists for a long tine, then it shows that Tomcat (or something within Tomcat) is not properly closing its end of client sockets, and that the objects containing these sockets are lingering on the Heap, waiting to be collected. I'm sure someone else on this list could suggest a scenario where a badly-behaved application could achieve this. (or a very large keepAlive setting ?) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 6 does not respond or freeze after startup
Hello, @Thread dumps: I attached some current thread.Directly after startup and after Tomcat stops responding. @Installation and start: I installed Tomcat directly from a zip file and runs it from the given scripts. @Prevented access: I have deactivated the firewall as well as the virus scanner. But Tomcat stops responding again. What else could I check? Thank you and kind regards, T. Gau Caldarale, Charles R schrieb am 05.08.2010 14:47: From: T. Gau [mailto:t...@normad.de] Subject: Re: Tomcat 6 does not respond or freeze after startup as I understand the netstat output the mentioned PID's are the client ports instead. You are correct, André misread the output. What seems conspiciuous is that the home page from http://localhost:8080 is loaded but the images to the apache foundation and the powered by are missing and the browser is showing as still loading. This still sounds like either a firewall is blocking traffic, or some kind of virus scanner is getting in the way on file accesses, or the account Tomcat is running under can't access the resources. How did you install Tomcat, and how are you running it? I'd suggest running it from scripts rather than as a service until you get things sorted. After the freeze of Tomcat the Firefox browser shows the "loading sign" for each request againsthttp://localhost:8080. There's no evidence that Tomcat is actually freezing, since you continue to see activity via VisualVM. It still appears that something external to Tomcat is preventing access. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail:users-unsubscr...@tomcat.apache.org For additional commands, e-mail:users-h...@tomcat.apache.org 2010-08-05 19:57:37 Full thread dump Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing): "RMI TCP Accept-0" daemon prio=6 tid=0x0305a800 nid=0x17c4 runnable [0x03aef000] java.lang.Thread.State: RUNNABLE at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:390) - locked <0x28130f38> (a java.net.SocksSocketImpl) at java.net.ServerSocket.implAccept(ServerSocket.java:453) at java.net.ServerSocket.accept(ServerSocket.java:421) at sun.management.jmxremote.LocalRMIServerSocketFactory$1.accept(LocalRMIServerSocketFactory.java:34) at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:369) at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:341) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None "TP-Monitor" daemon prio=6 tid=0x0305b800 nid=0x1704 in Object.wait() [0x0397f000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x281376a8> (a org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable) at org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPool.java:565) - locked <0x281376a8> (a org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None "TP-Processor4" daemon prio=6 tid=0x0331bc00 nid=0x1700 runnable [0x0392f000] java.lang.Thread.State: RUNNABLE at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:390) - locked <0x28137788> (a java.net.SocksSocketImpl) at java.net.ServerSocket.implAccept(ServerSocket.java:453) at java.net.ServerSocket.accept(ServerSocket.java:421) at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:312) at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:666) at org.apache.jk.common.ChannelSocket$SocketAcceptor.runIt(ChannelSocket.java:877) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) at java.lang.Thread.run(Thread.java:619) Locked ownable synchronizers: - None "TP-Processor3" daemon prio=6 tid=0x032f1800 nid=0x16fc in Object.wait() [0x038df000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x28137a30> (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Object.wait(Object.java:485) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:662) - locked <0x28137a30> (a org.apache.tomcat.ut
Re: Tomcat 6 does not respond or freeze after startup
Hello everybody, my problem seems to be solved. I uninstalled virus scanner, firewall and virtual box (as it has a virtual network adapter). And reinstalled these step by step until my Tomcat stops responding. I didn't want to beliefe but have to yield to reason. ;) The firewall was the culprit. Now I have to run with Windows Firewall for the time being. Thank you all for your kind support. Best regards, T. Gau André Warnier schrieb am 06.08.2010 13:16: ... Restarting a bit earlier in this conversation : The browser connections are shown (by netstat.exe) in the state "CLOSE_WAIT". The following page explains what that means : http://support.microsoft.com/kb/137984 If I understand this right, it means that the client has closed its side of the connection (by sending a FIN packet). The socket is now "half-closed", and the server should close its own side. However, the server does not do that, and these sockets stay half-closed (or half-opened, if you prefer). What puzzles me, is the fact that according to the state of the connections, the clients should have closed them, but you otherwise write that the browser(s) still seem to display the fact that they are waiting for something. You also say that the basic html page is loaded, but that the images are missing. It looks very much as if each browser can send one request (for the home page), and receives a response (the home page, html-only). But then, when the browser tries (on the same connection normally) to request one of the embedded images, it does not receive a response and keeps waiting for it. And the server seems to think that the browser has disconnected, but never closes its end of the socket. Obviously, something is seriously wrong somewhere, because this situation does not really make sense. But it does not really look like a Tomcat problem, and more like an underlying network issue. You have also mentioned that you disabled the Windows firewall, but had been running some other firewall software at some point (which is now also disabled). At this point, my suspicions would go very much in the direction of some interference by one or both of these firewall softwares. Maybe when you initially installed the add-on firewall, you did something wrong and now your Windows installation is somehow screwed up ? It is relatively easy under Windows to get into such a kind of mess, and relatively difficult to get out of it once it is there. In my experience, different firewall packages and/or VPN packages have a tendency to seriously interfere with eachother. You seem to have a problem of that category. Any chance of doing some "Windows repair" job before you continue ? At the very least, I would try to completely de-install the additional firewall software, and try again then. Just disabling that firewall may not be enough to really remove the links and callbacks it may have installed all over the place. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
