AW: Too many connections in keepalive state in jk threadpool

2012-03-05 Thread Beier Michael
Hallo Herr Jung, >-Ursprüngliche Nachricht- >Von: Rainer Jung [mailto:rainer.j...@kippdata.de] > >Hallo Herr Beier, > >On 02.03.2012 11:19, Beier Michael wrote: >> Hi all, >> >> we're running tomcat 7.0.23 on sun jdk 1.6.0_29, connected >

AW: AW: Too many connections in keepalive state in jk threadpool

2012-03-02 Thread Beier Michael
t;> Gesendet: Freitag, 2. März 2012 13:01 >> An: Tomcat Users List >> Betreff: Re: Too many connections in keepalive state in jk threadpool >> >> Beier Michael wrote: >>> Hi all, >>> >>> we're running tomcat 7.0.23 on sun jdk 1.6.0_29, connected

AW: Too many connections in keepalive state in jk threadpool

2012-03-02 Thread Beier Michael
Von: André Warnier [mailto:a...@ice-sa.com] Gesendet: Freitag, 2. März 2012 13:01 An: Tomcat Users List Betreff: Re: Too many connections in keepalive state in jk threadpool Beier Michael wrote: > Hi all, > > we're running tomcat 7.0.23 on sun jdk 1.6.0_29, connected via ajp to http

Too many connections in keepalive state in jk threadpool

2012-03-02 Thread Beier Michael
Hi all, we're running tomcat 7.0.23 on sun jdk 1.6.0_29, connected via ajp to httpd 2.2.21 using mod_jk 1.2.32. I observed the behavior, that tomcat keeps threads in its ajp pool in keepalive state, regardless of which timeouts (connectionTimeout and keepAliveTimeout) are configured in tomcat.