tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Warnier ...@ice-sa.com>
Subject Re: Tomcat 6 does not respond or freeze after startup
Date Wed, 04 Aug 2010 21:11:58 GMT
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


Mime
View raw message