tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephanie Wullbieter" <swu...@gmx.de>
Subject mod_jk keeps connections closed by tomcat in CLOSE_WAIT state
Date Mon, 26 May 2008 08:50:02 GMT
Hello,

with 
netstat -A inet
on the apache httpd side I see that ajp connections that are closed correctly by tomcat after
<connectionTimeout> ms are not closed by mod_jk allthough the socket_timeout (so named
in mod_jk 1.2.5, now called connection_pool_timeout) is the same time (in s).

these connections stay on mod_jk side in status CLOSE_WAIT with  Recv-Q = 1

Sometimes these connections are replaced by other connections with different dynamic ports
on the sender (mod_jk) side, maybe it's a reuse I do not know - I thought when reusing (pooling)
then the dynamic port has to be the same. Sometimes these connections are not used/replaced
for new requests.

Is that phenomen known?

Looks like these connections are only closed by the firewall after fw timeout.

Used software:
mod_jk 1.2.5 on Debian Woody
-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger

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


Mime
View raw message