You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "T. Gau" <tg...@normad.de> on 2010/08/02 23:29:30 UTC

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\docs
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/docs] reload 
resource D:\Entwicklung\apache-tomcat-6.0.29\conf\context.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/docs] reload 
resource D:\Entwicklung\apache-tomcat-6.0.29\webapps\docs\WEB-INF\web.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/docs] reload 
resource D:\Entwicklung\apache-tomcat-6.0.29\conf\web.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/examples] 
redeploy resource D:\Entwicklung\apache-tomcat-6.0.29\webapps\examples
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/examples] 
reload resource D:\Entwicklung\apache-tomcat-6.0.29\conf\context.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/examples] 
reload resource 
D:\Entwicklung\apache-tomcat-6.0.29\webapps\examples\WEB-INF\web.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/examples] 
reload resource D:\Entwicklung\apache-tomcat-6.0.29\conf\web.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/host-manager] 
redeploy resource D:\Entwicklung\apache-tomcat-6.0.29\webapps\host-manager
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/host-manager] 
redeploy resource 
D:\Entwicklung\apache-tomcat-6.0.29\conf\Catalina\localhost\host-manager.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/host-manager] 
reload resource 
D:\Entwicklung\apache-tomcat-6.0.29\webapps\host-manager\WEB-INF\web.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/host-manager] 
reload resource 
D:\Entwicklung\apache-tomcat-6.0.29\conf\Catalina\localhost\host-manager.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/host-manager] 
reload resource D:\Entwicklung\apache-tomcat-6.0.29\conf\context.xml
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.startup.HostConfig - Checking context[/host-manager] 
reload resource D:\Entwicklung\apache-tomcat-6.0.29\conf\web.xml
... [repeat checking context] ...
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.session.ManagerBase - Start expire sessions 
StandardManager at 1280783057406 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 1280783057406 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 1280783057406 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 1280783057406 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 1280783057406 sessioncount 0
DEBUG ContainerBackgroundProcessor[StandardEngine[Catalina]] 
org.apache.catalina.session.ManagerBase - End expire sessions 
StandardManager processingTime 0 expired sessions: 0
... [repeat checking context] ...





[2] Thread dump via VisualVM:
2010-08-02 23:15:31
Full thread dump Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing):

"RMI TCP Accept-0" daemon prio=6 tid=0x03180400 nid=0x428 runnable 
[0x04aaf000]
    java.lang.Thread.State: RUNNABLE
     at java.net.PlainSocketImpl.socketAccept(Native Method)
     at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:390)
     - locked <0x28248c30> (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

"ajp-8009-Acceptor-0" daemon prio=6 tid=0x0317cc00 nid=0xcfc runnable 
[0x0491f000]
    java.lang.Thread.State: RUNNABLE
     at org.apache.tomcat.jni.Socket.accept(Native Method)
     at 
org.apache.tomcat.util.net.AprEndpoint$Acceptor.run(AprEndpoint.java:1169)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-CometPoller-7" daemon prio=6 tid=0x0317b800 nid=0xf8c in 
Object.wait() [0x048cf000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281be900> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281be900> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-CometPoller-6" daemon prio=6 tid=0x0317a000 nid=0xdcc in 
Object.wait() [0x0487f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281be998> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281be998> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-CometPoller-5" daemon prio=6 tid=0x03175400 nid=0xe10 in 
Object.wait() [0x0482f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bea30> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bea30> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-CometPoller-4" daemon prio=6 tid=0x03173c00 nid=0x300 in 
Object.wait() [0x047df000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281beac8> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281beac8> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-CometPoller-3" daemon prio=6 tid=0x03172400 nid=0x398 in 
Object.wait() [0x0478f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281beb60> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281beb60> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-CometPoller-2" daemon prio=6 tid=0x03171000 nid=0x280 in 
Object.wait() [0x0473f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bebf8> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bebf8> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-CometPoller-1" daemon prio=6 tid=0x0316c400 nid=0x94c in 
Object.wait() [0x046ef000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bec90> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bec90> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-CometPoller-0" daemon prio=6 tid=0x0316ac00 nid=0x7d8 in 
Object.wait() [0x0469f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bed28> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bed28> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-Poller-7" daemon prio=6 tid=0x03150400 nid=0x918 in 
Object.wait() [0x0464f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bedc0> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bedc0> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-Poller-6" daemon prio=6 tid=0x03169800 nid=0x4b8 in 
Object.wait() [0x045ff000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bee58> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bee58> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-Poller-5" daemon prio=6 tid=0x0314e000 nid=0x8d0 in 
Object.wait() [0x045af000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281beef0> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281beef0> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-Poller-4" daemon prio=6 tid=0x03153c00 nid=0x674 in 
Object.wait() [0x0415f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bef88> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bef88> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-Poller-3" daemon prio=6 tid=0x03165800 nid=0x698 in 
Object.wait() [0x0410f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf020> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf020> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-Poller-2" daemon prio=6 tid=0x03160800 nid=0xf50 in 
Object.wait() [0x040bf000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf0b8> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf0b8> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-Poller-1" daemon prio=6 tid=0x03142800 nid=0x824 in 
Object.wait() [0x0406f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf150> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf150> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ajp-8009-Poller-0" daemon prio=6 tid=0x03147000 nid=0xeb4 in 
Object.wait() [0x0401f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf1e8> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf1e8> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Acceptor-0" daemon prio=6 tid=0x03141c00 nid=0xd74 runnable 
[0x03fcf000]
    java.lang.Thread.State: RUNNABLE
     at org.apache.tomcat.jni.Socket.accept(Native Method)
     at 
org.apache.tomcat.util.net.AprEndpoint$Acceptor.run(AprEndpoint.java:1169)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Sendfile-0" daemon prio=6 tid=0x0313e400 nid=0xbc in 
Object.wait() [0x03f7f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf2f8> (a 
org.apache.tomcat.util.net.AprEndpoint$Sendfile)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Sendfile.run(AprEndpoint.java:1805)
     - locked <0x281bf2f8> (a 
org.apache.tomcat.util.net.AprEndpoint$Sendfile)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-CometPoller-7" daemon prio=6 tid=0x0313d400 nid=0xdf0 in 
Object.wait() [0x03f2f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf390> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf390> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-CometPoller-6" daemon prio=6 tid=0x03134800 nid=0x140 in 
Object.wait() [0x03edf000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf428> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf428> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-CometPoller-5" daemon prio=6 tid=0x03133000 nid=0xda4 in 
Object.wait() [0x03e8f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf4c0> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf4c0> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-CometPoller-4" daemon prio=6 tid=0x03130c00 nid=0x9a4 in 
Object.wait() [0x03e3f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf558> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf558> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-CometPoller-3" daemon prio=6 tid=0x0312f400 nid=0x148 in 
Object.wait() [0x03def000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf5f0> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf5f0> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-CometPoller-2" daemon prio=6 tid=0x0313c000 nid=0xbc4 in 
Object.wait() [0x03d9f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf688> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf688> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-CometPoller-1" daemon prio=6 tid=0x0313a800 nid=0xaa0 in 
Object.wait() [0x03d4f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf720> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf720> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-CometPoller-0" daemon prio=6 tid=0x03139400 nid=0xb50 in 
Object.wait() [0x03cff000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf7b8> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf7b8> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Poller-7" daemon prio=6 tid=0x03138400 nid=0x878 in 
Object.wait() [0x03caf000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf850> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf850> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Poller-6" daemon prio=6 tid=0x0312b800 nid=0xe94 in 
Object.wait() [0x03c5f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf8e8> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf8e8> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Poller-5" daemon prio=6 tid=0x0312a400 nid=0xe48 in 
Object.wait() [0x03a0f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bf980> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bf980> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Poller-4" daemon prio=6 tid=0x03128c00 nid=0x710 in 
Object.wait() [0x039bf000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bfa18> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bfa18> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Poller-3" daemon prio=6 tid=0x03118800 nid=0xa44 in 
Object.wait() [0x0396f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bfab0> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bfab0> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Poller-2" daemon prio=6 tid=0x03148400 nid=0x16c in 
Object.wait() [0x0391f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bfb48> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bfb48> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Poller-1" daemon prio=6 tid=0x03131400 nid=0xe14 in 
Object.wait() [0x038cf000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bfbe0> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bfbe0> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"http-8080-Poller-0" daemon prio=6 tid=0x03155400 nid=0xa90 in 
Object.wait() [0x0387f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x281bfc78> (a 
org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Object.wait(Object.java:485)
     at 
org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1336)
     - locked <0x281bfc78> (a org.apache.tomcat.util.net.AprEndpoint$Poller)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"ContainerBackgroundProcessor[StandardEngine[Catalina]]" daemon prio=6 
tid=0x03152800 nid=0x4e8 waiting on condition [0x0382f000]
    java.lang.Thread.State: TIMED_WAITING (sleeping)
     at java.lang.Thread.sleep(Native Method)
     at 
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1579)
     at java.lang.Thread.run(Thread.java:619)

    Locked ownable synchronizers:
     - None

"GC Daemon" daemon prio=2 tid=0x03047800 nid=0x270 in Object.wait() 
[0x0364f000]
    java.lang.Thread.State: TIMED_WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x27ff5518> (a sun.misc.GC$LatencyLock)
     at sun.misc.GC$Daemon.run(GC.java:100)
     - locked <0x27ff5518> (a sun.misc.GC$LatencyLock)

    Locked ownable synchronizers:
     - None

"Low Memory Detector" daemon prio=6 tid=0x02b1e800 nid=0xe08 runnable 
[0x00000000]
    java.lang.Thread.State: RUNNABLE

    Locked ownable synchronizers:
     - None

"CompilerThread0" daemon prio=10 tid=0x02b18000 nid=0x920 waiting on 
condition [0x00000000]
    java.lang.Thread.State: RUNNABLE

    Locked ownable synchronizers:
     - None

"Attach Listener" daemon prio=10 tid=0x02b16800 nid=0x194 waiting on 
condition [0x00000000]
    java.lang.Thread.State: RUNNABLE

    Locked ownable synchronizers:
     - None

"Signal Dispatcher" daemon prio=10 tid=0x02b15400 nid=0x978 runnable 
[0x00000000]
    java.lang.Thread.State: RUNNABLE

    Locked ownable synchronizers:
     - None

"Finalizer" daemon prio=8 tid=0x02b10c00 nid=0xa28 in Object.wait() 
[0x02cdf000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x27ee0be8> (a java.lang.ref.ReferenceQueue$Lock)
     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)
     - locked <0x27ee0be8> (a java.lang.ref.ReferenceQueue$Lock)
     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)
     at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

    Locked ownable synchronizers:
     - None

"Reference Handler" daemon prio=10 tid=0x02b0c000 nid=0x4c0 in 
Object.wait() [0x02c8f000]
    java.lang.Thread.State: WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     - waiting on <0x27ee0c70> (a java.lang.ref.Reference$Lock)
     at java.lang.Object.wait(Object.java:485)
     at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
     - locked <0x27ee0c70> (a java.lang.ref.Reference$Lock)

    Locked ownable synchronizers:
     - None

"main" prio=6 tid=0x002b7400 nid=0x9cc runnable [0x0090f000]
    java.lang.Thread.State: RUNNABLE
     at java.net.PlainSocketImpl.socketAccept(Native Method)
     at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:390)
     - locked <0x281bfd68> (a java.net.SocksSocketImpl)
     at java.net.ServerSocket.implAccept(ServerSocket.java:453)
     at java.net.ServerSocket.accept(ServerSocket.java:421)
     at 
org.apache.catalina.core.StandardServer.await(StandardServer.java:389)
     at org.apache.catalina.startup.Catalina.await(Catalina.java:662)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:614)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

    Locked ownable synchronizers:
     - None

"VM Thread" prio=10 tid=0x02b0a800 nid=0xbf0 runnable

"VM Periodic Task Thread" prio=10 tid=0x02b20c00 nid=0x7fc waiting on 
condition

JNI global references: 709




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: [OT] Tomcat 6 does not respond or freeze after startup

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck,

On 8/5/2010 11:54 AM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:chris@christopherschultz.net]
>> Subject: Re: [OT] Tomcat 6 does not respond or freeze after startup
>>
>> Yup. I think Microsoft's PRNG is implemented something like this:
>>
>> long int random() {
>>   return time() % 2;
>> }
>>
>> Super efficient!
> 
> I think you left out the requisite buffer overflow built into every Windows API...

How about this:

long int random() {
  return *(time()) % 2;
}
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxa4WUACgkQ9CaO5/Lv0PBpngCgnBxEAtdTpdOTWvZ0BipTHjKZ
Li0AnR60qrHkx/UDxjHZXziqshhMQMp+
=CXa9
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: [OT] Tomcat 6 does not respond or freeze after startup

Posted by André Warnier <aw...@ice-sa.com>.
Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:chris@christopherschultz.net]
>> Subject: Re: [OT] Tomcat 6 does not respond or freeze after startup
>>
>> Yup. I think Microsoft's PRNG is implemented something like this:
>>
>> long int random() {
>>   return time() % 2;
>> }
>>
>> Super efficient!
> 
> I think you left out the requisite buffer overflow built into every Windows API...
> 
And the message about the new Windows Media Player download every time the above function 
returns 1.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: [OT] Tomcat 6 does not respond or freeze after startup

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Subject: Re: [OT] Tomcat 6 does not respond or freeze after startup
> 
> Yup. I think Microsoft's PRNG is implemented something like this:
> 
> long int random() {
>   return time() % 2;
> }
> 
> Super efficient!

I think you left out the requisite buffer overflow built into every Windows API...

 - 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.


Re: [OT] Tomcat 6 does not respond or freeze after startup

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck,

On 8/5/2010 8:39 AM, Caldarale, Charles R wrote:
>> From: Rainer Jung [mailto:rainer.jung@kippdata.de]
>> Subject: Re: Tomcat 6 does not respond or freeze after startup
>>
>> Did we already see a full thread dump?
> 
> Yes: http://marc.info/?l=tomcat-user&m=128078460930111&w=2
> 
>> <WildGuess>Could it be blocked by entropy gathering for random
>> initialization?<WildGuess/>
> 
> Probably not - this is on Windows.

Yup. I think Microsoft's PRNG is implemented something like this:

long int random() {
  return time() % 2;
}

Super efficient!

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxa3cYACgkQ9CaO5/Lv0PDADwCfW849U741XZ74JUpB0qRp9y93
uG0AmwZVm9gYAsX9xvLdB2PqiHsvhJma
=Z8GT
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat 6 does not respond or freeze after startup

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Rainer Jung [mailto:rainer.jung@kippdata.de]
> Subject: Re: Tomcat 6 does not respond or freeze after startup
> 
> Did we already see a full thread dump?

Yes: http://marc.info/?l=tomcat-user&m=128078460930111&w=2

> <WildGuess>Could it be blocked by entropy gathering for random
> initialization?<WildGuess/>

Probably not - this is on 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by Rainer Jung <ra...@kippdata.de>.
On 04.08.2010 22:54, T. Gau wrote:
> Hello,
>
> I have executed 'netstat -anopb tcp' with the following result:
> TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING 3436 [java.exe]
> TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 3436 [java.exe]
> TCP 127.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
> TCP 127.0.0.1:8080 127.0.0.1:2049 CLOSE_WAIT 3436 [java.exe]
> TCP 127.0.0.1:8080 127.0.0.1:2050 CLOSE_WAIT 3436 [java.exe]
> TCP 127.0.0.1:8080 127.0.0.1:1992 CLOSE_WAIT 3436 [java.exe]
> TCP 127.0.0.1:8080 127.0.0.1:1991 CLOSE_WAIT 3436 [java.exe]
> TCP 127.0.0.1:8080 127.0.0.1:2051 CLOSE_WAIT 3436 [java.exe]
> TCP 127.0.0.1:8080 127.0.0.1:1990 CLOSE_WAIT 3436 [java.exe]
> TCP 127.0.0.1:8080 127.0.0.1:1989 CLOSE_WAIT 3436 [java.exe]
> TCP 127.0.0.1:8080 127.0.0.1:2043 CLOSE_WAIT 3436 [java.exe]
> TCP 127.0.0.1:8080 127.0.0.1:2042 CLOSE_WAIT 3436 [java.exe]
> Any ideas what happens here?

Did we already see a full thread dump?

<WildGuess>Could it be blocked by entropy gathering for random 
initialization?<WildGuess/>

Regards,

Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by André Warnier <aw...@ice-sa.com>.
T. Gau wrote:
...

> 
> Caldarale, Charles R schrieb am 05.08.2010 14:47:
>>> From: T. Gau [mailto:tgau@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.
>>
Yes, my mistake, sorry.

>>> 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.
...
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by Rainer Jung <ra...@kippdata.de>.
On 05.08.2010 22:52, T. Gau wrote:
> Hello,
>
> @Thread dumps:
> I attached some current thread.Directly after startup and after Tomcat
> stops responding.

Sorry, no idea here. Nothing obvious wrong in those dumps.

Regards,

Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  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:tgau@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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail:users-help@tomcat.apache.org
>


RE: Tomcat 6 does not respond or freeze after startup

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: T. Gau [mailto:tgau@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 against http://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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  Hello,

as I understand the netstat output the mentioned PID's are the client 
ports instead.

I'm just calling http://localhost:8080 via a web browser, e.g. Firefox. 
Following the history of my calls against Tomcat:

Proto  Lokale Adresse         Remoteadresse          Status           PID
After startup
TCP    0.0.0.0:8009           0.0.0.0:0              LISTENING         
2408    [java.exe]
TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING         
2408    [java.exe]
TCP    127.0.0.1:8005         0.0.0.0:0              LISTENING         
2408    [java.exe]

After first successfull accesses to Tomcat (http://localhost:8080)
TCP    127.0.0.1:1255         127.0.0.1:8080         CONNECTED     
3568    [firefox.exe]
TCP    127.0.0.1:1256         127.0.0.1:8080         CONNECTED     
3568    [firefox.exe]
TCP    127.0.0.1:1257         127.0.0.1:8080         CONNECTED     
3568    [firefox.exe]
TCP    127.0.0.1:8080         127.0.0.1:1256         CONNECTED     
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1257         CONNECTED     
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1255         CONNECTED     
2408    [java.exe]
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.


After some more accesses, Tomcat freezed
TCP    127.0.0.1:1256         127.0.0.1:8080         CONNECTED     
3568    [firefox.exe]
TCP    127.0.0.1:1257         127.0.0.1:8080         CONNECTED     
3568    [firefox.exe]
TCP    127.0.0.1:8080         127.0.0.1:1256         CONNECTED     
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1257         CONNECTED     
2408    [java.exe]
TCP    127.0.0.1:1261         127.0.0.1:8080         FIN_WAIT_2    
3568    [firefox.exe]
TCP    127.0.0.1:1262         127.0.0.1:8080         FIN_WAIT_2    
3568    [firefox.exe]
TCP    127.0.0.1:1263         127.0.0.1:8080         FIN_WAIT_2    
3568    [firefox.exe]
TCP    127.0.0.1:1264         127.0.0.1:8080         FIN_WAIT_2    
3568    [firefox.exe]
TCP    127.0.0.1:8080         127.0.0.1:1263         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1261         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1264         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1262         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1255         WAITING         0

... and again some accesses
TCP    127.0.0.1:1256         127.0.0.1:8080         CONNECTED     
3568    [firefox.exe]
TCP    127.0.0.1:1257         127.0.0.1:8080         CONNECTED     
3568    [firefox.exe]
TCP    127.0.0.1:8080         127.0.0.1:1257         CONNECTED     
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1256         CONNECTED     
2408    [java.exe]
TCP    127.0.0.1:1265         127.0.0.1:8080         FIN_WAIT_2    
3568    [firefox.exe]
TCP    127.0.0.1:1266         127.0.0.1:8080         FIN_WAIT_2    
3568    [firefox.exe]
TCP    127.0.0.1:1267         127.0.0.1:8080         FIN_WAIT_2    
3568    [firefox.exe]
TCP    127.0.0.1:1268         127.0.0.1:8080         FIN_WAIT_2    
3568    [firefox.exe]
TCP    127.0.0.1:8080         127.0.0.1:1265         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1264         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1263         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1262         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1261         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1266         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1267         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1268         CLOSE_WAIT    
2408    [java.exe]

After some waiting
TCP    127.0.0.1:1256         127.0.0.1:8080         CONNECTED     
3568    [firefox.exe]
TCP    127.0.0.1:1257         127.0.0.1:8080         CONNECTED     
3568    [firefox.exe]
TCP    127.0.0.1:8080         127.0.0.1:1257         CONNECTED     
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1256         CONNECTED     
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1265         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1267         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1264         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1263         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1262         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1261         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1268         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1266         CLOSE_WAIT    
2408    [java.exe]

After closing tomcat
TCP    127.0.0.1:1256         127.0.0.1:8080         FIN_WAIT_2    
3568    [System]
TCP    127.0.0.1:1257         127.0.0.1:8080         FIN_WAIT_2    
3568    [System]
TCP    127.0.0.1:8080         127.0.0.1:1267         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1257         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1265         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1256         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1268         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1264         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1263         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1262         CLOSE_WAIT    
2408    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1266         CLOSE_WAIT    
2408    [java.exe]
TCP    127.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:
>>>> TCP    0.0.0.0:8009           0.0.0.0:0              
>>>> LISTENING        3436    [java.exe]
>>>> TCP    0.0.0.0:8080           0.0.0.0:0              
>>>> LISTENING        3436    [java.exe]
>>>> TCP    127.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
>>>> TCP    127.0.0.1:8080         127.0.0.1:2049         CLOSE_WAIT    
>>>> 3436    [java.exe]
>>>> TCP    127.0.0.1:8080         127.0.0.1:2050         CLOSE_WAIT    
>>>> 3436    [java.exe]
>>>> TCP    127.0.0.1:8080         127.0.0.1:1992         CLOSE_WAIT    
>>>> 3436    [java.exe]
>>>> TCP    127.0.0.1:8080         127.0.0.1:1991         CLOSE_WAIT    
>>>> 3436    [java.exe]
>>>> TCP    127.0.0.1:8080         127.0.0.1:2051         CLOSE_WAIT    
>>>> 3436    [java.exe]
>>>> TCP    127.0.0.1:8080         127.0.0.1:1990         CLOSE_WAIT    
>>>> 3436    [java.exe]
>>>> TCP    127.0.0.1:8080         127.0.0.1:1989         CLOSE_WAIT    
>>>> 3436    [java.exe]
>>>> TCP    127.0.0.1:8080         127.0.0.1:2043         CLOSE_WAIT    
>>>> 3436    [java.exe]
>>>> TCP    127.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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by André Warnier <aw...@ice-sa.com>.
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:
>>> TCP    0.0.0.0:8009           0.0.0.0:0              LISTENING        
>>> 3436    [java.exe]
>>> TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING        
>>> 3436    [java.exe]
>>> TCP    127.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
>>> TCP    127.0.0.1:8080         127.0.0.1:2049         CLOSE_WAIT    
>>> 3436    [java.exe]
>>> TCP    127.0.0.1:8080         127.0.0.1:2050         CLOSE_WAIT    
>>> 3436    [java.exe]
>>> TCP    127.0.0.1:8080         127.0.0.1:1992         CLOSE_WAIT    
>>> 3436    [java.exe]
>>> TCP    127.0.0.1:8080         127.0.0.1:1991         CLOSE_WAIT    
>>> 3436    [java.exe]
>>> TCP    127.0.0.1:8080         127.0.0.1:2051         CLOSE_WAIT    
>>> 3436    [java.exe]
>>> TCP    127.0.0.1:8080         127.0.0.1:1990         CLOSE_WAIT    
>>> 3436    [java.exe]
>>> TCP    127.0.0.1:8080         127.0.0.1:1989         CLOSE_WAIT    
>>> 3436    [java.exe]
>>> TCP    127.0.0.1:8080         127.0.0.1:2043         CLOSE_WAIT    
>>> 3436    [java.exe]
>>> TCP    127.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-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  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:
>> TCP    0.0.0.0:8009           0.0.0.0:0              LISTENING        
>> 3436    [java.exe]
>> TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING        
>> 3436    [java.exe]
>> TCP    127.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
>> TCP    127.0.0.1:8080         127.0.0.1:2049         CLOSE_WAIT    
>> 3436    [java.exe]
>> TCP    127.0.0.1:8080         127.0.0.1:2050         CLOSE_WAIT    
>> 3436    [java.exe]
>> TCP    127.0.0.1:8080         127.0.0.1:1992         CLOSE_WAIT    
>> 3436    [java.exe]
>> TCP    127.0.0.1:8080         127.0.0.1:1991         CLOSE_WAIT    
>> 3436    [java.exe]
>> TCP    127.0.0.1:8080         127.0.0.1:2051         CLOSE_WAIT    
>> 3436    [java.exe]
>> TCP    127.0.0.1:8080         127.0.0.1:1990         CLOSE_WAIT    
>> 3436    [java.exe]
>> TCP    127.0.0.1:8080         127.0.0.1:1989         CLOSE_WAIT    
>> 3436    [java.exe]
>> TCP    127.0.0.1:8080         127.0.0.1:2043         CLOSE_WAIT    
>> 3436    [java.exe]
>> TCP    127.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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by André Warnier <aw...@ice-sa.com>.
Hi T.

T. Gau wrote:
>  Hello,
> 
> I have executed 'netstat -anopb tcp' with the following result:
> TCP    0.0.0.0:8009           0.0.0.0:0              LISTENING        
> 3436    [java.exe]
> TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING        
> 3436    [java.exe]
> TCP    127.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
> TCP    127.0.0.1:8080         127.0.0.1:2049         CLOSE_WAIT    
> 3436    [java.exe]
> TCP    127.0.0.1:8080         127.0.0.1:2050         CLOSE_WAIT    
> 3436    [java.exe]
> TCP    127.0.0.1:8080         127.0.0.1:1992         CLOSE_WAIT    
> 3436    [java.exe]
> TCP    127.0.0.1:8080         127.0.0.1:1991         CLOSE_WAIT    
> 3436    [java.exe]
> TCP    127.0.0.1:8080         127.0.0.1:2051         CLOSE_WAIT    
> 3436    [java.exe]
> TCP    127.0.0.1:8080         127.0.0.1:1990         CLOSE_WAIT    
> 3436    [java.exe]
> TCP    127.0.0.1:8080         127.0.0.1:1989         CLOSE_WAIT    
> 3436    [java.exe]
> TCP    127.0.0.1:8080         127.0.0.1:2043         CLOSE_WAIT    
> 3436    [java.exe]
> TCP    127.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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  Hello,

I have executed 'netstat -anopb tcp' with the following result:
TCP    0.0.0.0:8009           0.0.0.0:0              LISTENING        
3436    [java.exe]
TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING        
3436    [java.exe]
TCP    127.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
TCP    127.0.0.1:8080         127.0.0.1:2049         CLOSE_WAIT    
3436    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:2050         CLOSE_WAIT    
3436    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1992         CLOSE_WAIT    
3436    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1991         CLOSE_WAIT    
3436    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:2051         CLOSE_WAIT    
3436    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1990         CLOSE_WAIT    
3436    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:1989         CLOSE_WAIT    
3436    [java.exe]
TCP    127.0.0.1:8080         127.0.0.1:2043         CLOSE_WAIT    
3436    [java.exe]
TCP    127.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:tgau@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:8009    0.0.0.0:0  LISTENING  4720
>    TCP  0.0.0.0:8080    0.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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat 6 does not respond or freeze after startup

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: T. Gau [mailto:tgau@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:8009    0.0.0.0:0  LISTENING  4720
  TCP  0.0.0.0:8080    0.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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  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:tgau@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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat 6 does not respond or freeze after startup

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: T. Gau [mailto:tgau@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  Check: No IPv6.


Kind regards.


Caldarale, Charles R schrieb am 04.08.2010 23:23:
>> From: T. Gau [mailto:tgau@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat 6 does not respond or freeze after startup

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: T. Gau [mailto:tgau@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.


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chuck,

On 8/4/2010 10:01 AM, Caldarale, Charles R wrote:
>> From: Christopher Schultz [mailto:chris@christopherschultz.net]
>> Subject: Re: Tomcat 6 does not respond or freeze after startup
>>
>>> As fas as I know, I'm not running IPv6. IPconfig doesn't show 
>>> any IPv6 specific.
>>
>> Sure? From your own log file:
>>
>> INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
>> [false], random [true].
> 
> I believe that the IPv6 [true] for APR shown above means only that APR was built with IPv6 support, not that IPv6 is actually available.

Gotcha.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxZc0oACgkQ9CaO5/Lv0PAtuACgtHxWH7MPyp1WsYmLGbizzRSK
i2MAoIuj6Co0oYznMFWrhMWdhuLlloBc
=M0R4
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat 6 does not respond or freeze after startup

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Christopher Schultz [mailto:chris@christopherschultz.net]
> Subject: Re: Tomcat 6 does not respond or freeze after startup
> 
> > As fas as I know, I'm not running IPv6. IPconfig doesn't show 
> > any IPv6 specific.
>
> Sure? From your own log file:
> 
> INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
> [false], random [true].

I believe that the IPv6 [true] for APR shown above means only that APR was built with IPv6 support, not that IPv6 is actually available.

 - 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.


Re: Tomcat 6 does not respond or freeze after startup

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  @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:tgau@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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat 6 does not respond or freeze after startup

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: T. Gau [mailto:tgau@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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  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
>> <empty>
>>
>> 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
>> <empty>
>>
>> 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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by Mark Thomas <ma...@apache.org>.
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
> <empty>
> 
> 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
> <empty>
> 
> 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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by "T. Gau" <tg...@normad.de>.
  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
<empty>

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
<empty>

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-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat 6 does not respond or freeze after startup

Posted by Mark Thomas <ma...@apache.org>.
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org