>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, > >many thanks for Your answer.
many thanks for your feedback, too. > >It looks, like the parameter reply_timeout=1800000 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 >vacation in another way. >[...] >Why the backend applications so often do not give any response, I think is >another issue for the developers. > >But maybe the importance of changing the reply_timeout parameter from default >value "infinit" to a even very high value of >30 min should be stated even more prominent in the worker documentation. I set this even lower (to 120s) because it's said it's the timeout for reading of each packet and no application on the Tomcat should take so much time to send any part of an answers. I might be of worth if you pass the URIs of the dangling requests to developers. Because not finished, they are not logged. But you may take a look on the scoreboards of the Apache or the Tomcat. On Tomcat, it available via an MBean, you may read out it via JMX or via the http-proxy of the Tomcat Manager application. I may send you a script as a pointer, if you like. Guido
