Thanks for Your answer. There are at least two (watchdog) ajp requests through the web server to the workers every minute, and as i wrote, the ajp connection_pool_timeout ist 600, connectionTimeout in Tomcats server.xml is accordingly 600000. So I cannot image how the web server can be more idle than the pool timeout, even at busy daytime, where the log messages also occure every few minutes?
We will look forward to upgrade to 1.2.26. 2009/1/27 Rainer Jung <rainer.j...@kippdata.de> > > Without additional error level messages that's OK. The web server noticed, > that there was no connection to the backend open and will transparently > create a new one. This could happen, if your web server is more idle than > configured with the JK connection pool timeout or Tomcat's > connectionTimeout. > > You should update to 1.2.27, it's better than 1.2.23 :) > >
