On 15.07.2011 12:09, Edward Quick wrote:
> Thanks for your replies. I found the solution was to set JkWatchdogInterval
> (by default this is not on). I set it to 30, and observed the FIN_WAIT
> disappears after 60 seconds (this could be the worker.maintain setting?) and
> the CLOSE_WAIT thread d
connection_pool_timeout.
Does this mean connection_pool_timeout only works if JkWatchdogInterval is
swithed on?
Ed.
-Original Message-
From: Rainer Jung [mailto:rainer.j...@kippdata.de]
Sent: 13 July 2011 23:23
To: users@tomcat.apache.org
Subject: Re: mod_jk question about lingering close_waits
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 7/13/2011 5:16 PM, André Warnier wrote:
> 1) this is the right list for Apache/Tomcat connectors (mod_jk among
> them)
Yes. When the question is about mod_proxy_ajp, we usually try our best
but defer to the Apache httpd user's list when thi
On 13.07.2011 23:16, André Warnier wrote:
> Hi.
>
> I am not the one who can really answer your question, but
>
> 1) this is the right list for Apache/Tomcat connectors (mod_jk among them)
>
> 2) a question : do these CLOSE_WAIT sockets bother you for some specific
> reason ?
> In a totally diff
Hi.
I am not the one who can really answer your question, but
1) this is the right list for Apache/Tomcat connectors (mod_jk among them)
2) a question : do these CLOSE_WAIT sockets bother you for some specific reason
?
In a totally different context, I have had problems with Linux systems when
Hi,
Apologies in advance if this is the wrong mailing list. I was unable to find
one specific to mod_jk and this looked the most relevant.
I have the following apache tomcat server configuration set up: Apache 2.2.3 ,
mod_jk 1.2.32 , and tomcat 6.0.32 running HelloWorld.war
If I send a request
