>From: Hildegard Meier [mailto:daku8...@gmx.de]
>Sent: Thursday, September 01, 2016 10:14 AM
>To: users@tomcat.apache.org
>Subject: [SOLVED] mod_jk/1.2.37 Apache/2.4.7 (Ubuntu): AJP established
>connections pile up, connection_pool_timeout has
>no effect?
>
>Dear Guido,
Dear Guido,
many thanks for Your answer.
It looks, like the parameter reply_timeout=180 was the solution. I added
that parameter yesterday and was not sure if that would help and since I go to
vacation in short time, I asked in this list in parallel to maybe solve the
problem before
Dear Hildegard,
I wrote:
>Note that the AJP connection pool is used per child (and per tomcat backend
>definition if you're using more than one). You
>use connection_pool_minsize=1. Please also note, that the spare threads will
>no gather to the lowest possible number of
>childs. May this
users@tomcat.apache.org
>Subject: mod_jk/1.2.37 Apache/2.4.7 (Ubuntu): AJP established connections pile
>up, connection_pool_timeout has no effect?
>
>Running:
>Ubuntu Trusty 14.0.4 LTS 64 Bit
>mod_jk/1.2.37
>Apache/2.4.7 (Ubuntu)
>
>Hello,
>
>I have much investi
mcat.apache.org
> Betreff: mod_jk/1.2.37 Apache/2.4.7 (Ubuntu): AJP established connections
> pile up, connection_pool_timeout has no effect?
>
> We have the following /etc/libapache2-mod-jk/workers.properties:
>
> ---
>
> # not used
> workers.tomcat_home=/usr/share/tomcat6
&
Running:
Ubuntu Trusty 14.0.4 LTS 64 Bit
mod_jk/1.2.37
Apache/2.4.7 (Ubuntu)
Hello,
I have much investigated into this, but have no idea, why the AJP connections
from the Apache (MPM worker) to the AJP backends pile up.
They do not get closed, they stay in state ESTABLISHED.
Over night, the
