[SOLVED] mod_jk/1.2.37 Apache/2.4.7 (Ubuntu): AJP established connections pile up, connection_pool_timeout has no effect?

2016-09-01 Thread Hildegard Meier
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

Aw: mod_jk/1.2.37 Apache/2.4.7 (Ubuntu): AJP established connections pile up, connection_pool_timeout has no effect?

2016-08-31 Thread Hildegard Meier
P.S. in workers.properties we use the template then with worker.myhost.reference=worker.template_01 worker.myhost.host=10.20.30.40 worker.myhost.port=8809 > Gesendet: Mittwoch, 31. August 2016 um 14:10 Uhr > Von: "Hildegard Meier" <daku8...@gmx.de> > An: users@to

mod_jk/1.2.37 Apache/2.4.7 (Ubuntu): AJP established connections pile up, connection_pool_timeout has no effect?

2016-08-31 Thread Hildegard Meier
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