Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates
 212.85.38.228 as permitted sender)
Message-ID: <5142FC26.5060609@ice-sa.com>
Date: Fri, 15 Mar 2013 11:47:02 +0100
From: =?ISO-8859-15?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
Reply-To: Tomcat Users List <users@tomcat.apache.org>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: AJP suddenly Stopps acting: ajp on 7009 and 9009 : connections
 keept open
References: 
 <08E5CE5F1D6E3145B4FA31AA948C54FE2B4ABEF4@x-dag01><08E5CE5F1D6E3145B4FA31AA948C54FE2B4AD91C@x-dag01><08E5CE5F1D6E3145B4FA31AA948C54FE2B4AD948@x-dag01><50F836FB.3010206@christopherschultz.net>
  <08E5CE5F1D6E3145B4FA31AA948C54FE2B4B0266@x-dag01><08E5CE5F1D6E3145B4FA31AA948C54FE2B4B028A@x-dag01><50F910A1.7000201@ice-sa.com><08E5CE5F1D6E3145B4FA31AA948C54FE2B4B03FC@x-dag01><50F91F78.8030203@ice-sa.com><08E5CE5F1D6E3145B4FA31AA948C54FE2B4B057B@x-dag01><08E5CE5F1D6E3145B4FA31AA948C54FE2B4B402F@x-dag01><08E5CE5F1D6E3145B4FA31AA948C54FE2B5513DA@x-dag01><513EED2C.4020402@ice-sa.com><08E5CE5F1D6E3145B4FA31AA948C54FE2B552E4C@x-dag01><514060C8.6060601@ice-sa.com><08E5CE5F1D6E3145B4FA31AA948C54FE2B5543D3@x-dag01><08E5CE5F1D6E3145B4FA31AA948C54FE2B5549EE@x-dag01><5140E466.2070207@ice-sa.com><08E5CE5F1D6E3145B4FA31AA948C54FE2B554D8B@x-dag01><51419090.7030102@ice-sa.com>
 <08E5CE5F1D6E3145B4FA31AA948C54FE2B556138@x-dag01>
 <5142F3BA.6090907@kippdata.de>
In-Reply-To: <5142F3BA.6090907@kippdata.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

Rainer Jung wrote:
> On 14.03.2013 10:04, David Kumar wrote:
>> Hey,
>>
>> thanks for note..
>> Attached you can find a new list.
>> So, java is keeping these connections in close_wait.
> 
> close_wait for an AJP connection seen from Tomcat means the other side -
> mod_jk - has closed the connection, but not Tomcat.
> 
> This is often due to a shorter Timeout on the mod_jk side than on the
> Tomcat side. It is not a problem per se, but it is if it happens for too
> many connections for a too long time.
> 
> I vaguely remember that you have a 10 second socket_timeout in your
> workers.properties. That's typically bad. Look at the example config in
> the source mod_jk download.
> 
> It could be, that your requests in Tomcat got stuck and Tomcat still is
> in the state of working on the requests, therefore keeping the
> connection open to send back stuff finally, whereas mod_jk has already
> timed out. To check for that, take a cou�ple of threa dumps (not: heap
> dumps) of the running Tomcat process while the close_wait problem is
> visible. Check what your Tomcat threads are currently doing, e.g. are
> they mostly sitting idle in the thread pool or executor, or are many of
> them deep in your application stacks and waiting for database, locks or
> other stuff.
> 

Hi Rainer, a question to you :

In a previous post, David posted the output of "netstat -t -pan".
In that output, there are about 1900 connections from Apache to Tomcat's AJP connectors, 
in state "TIME_WAIT".
As far as I know, this indicates that the connection is closed from the point of view of 
Apache, and this TIME_WAIT should last only a few sec. maximum, and then should go away.
Why does he have so many though ? I can't see anything like that on any of my servers.

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