tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Fourel" <>
Subject Re: Tomcat 5.5 hanged . Thread Dump Analyze
Date Wed, 16 Jul 2008 12:09:55 GMT
There are 373 threads from the http connector pool at port 8180 (what's the
configuration of this connector in server.xml?)

The configuration is :
        <Connector port="8180" maxHttpHeaderSize="8192"
                   maxThreads="1500" minSpareThreads="100"
                   enableLookups="false" acceptCount="300"
                   connectionTimeout="600000" disableUploadTimeout="true"

What exactly do you mean by "hanged"?
We have a C++ client that send requests to this port. In a normal situation
Tomcat read the request and execute it. When it is "hanged" Tomcat doesnt
accept request from the c++ client. The already opened connection use all
the available sockets that are never closed. In the TCP logs we see that the
client send an ACK1 and Tomcat does the same (they should proceed to ACK2 an
finish the process).

On Wed, Jul 16, 2008 at 11:40 AM, Rainer Jung <>

> Olivier Fourel schrieb:
>  Hello all,
>> our Tomcat production server hanged again.
>> We made 2 thread dumps with few minutes between them.
>> I used TDA but didn"t find any clear reason for the Tomcat state which
>> stop answering request. In fact, It opens more and more socket without
>> release them and from our client when we try to get a new connection we
>> never receive any answer from Tomcat.
>> Any help with interpretating theses 2 dumps would be very nice.
>> The 2 dumps are joined in a zip as attached file.
> There are 373 threads from the http connector pool at port 8180 (what's the
> configuration of this connector in server.xml?). In dump 1 there are 295 of
> them in "parseRequestLine()", so I would say they are doing HTTP Keep-Alive
> and wait for the next request in an already established connection, 77 are
> idle in the pool and one is waiting in accept() for the next connection to
> come in.
> In dump 2 there are 157 threads in "parseRequestLine()" on Port 8180 and
> 215 idle in the pool, again 1 waiting in accept().
> It doesn't look very strange. What exactl do you mean by "hanged"?
> What happens if telnet from the local host to port 8180 and type
> GET / HTTP/1.0
> (two returns). Do you get an answer?
> Do you have any OutOfMemoryError in your log files?
> Regards,
> Rainer
> ---------------------------------------------------------------------
> To start a new topic, e-mail:
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message