On 25/01/2019 23:11, James H. H. Lampert wrote: > This is also about our clustered Tomcat 8 application running on Google > Cloud. > > The Report sub-cluster runs BIRT. And the default landing page is the > Eclipse BIRT viewer default landing page, the one that shows an Eclipse > logo, and says "BIRT viewer has been installed." > > I've got a health-check on that sub-cluster, that polls the default > landing page of ROOT periodically. Up until a few days ago, it was > polling it every 5 seconds; earlier this week, I cut it down to every 5 > minutes (the maximum); now I've got it at every 30 seconds. > > If I open the Manager context, I find that it shows (currently) around > 180 sessions for the ROOT context. When it was going every 5 minutes, it > was showing 18 sessions; when it was going every 5 seconds, it was up to > over a thousand. > > The other two sub-clusters don't have any dangling sessions from their > health-checks; why would this one? > > I'd like the sessions from all this health-check polling to expire a bit > more quickly; can anybody here suggest a way to accomplish that?
http://tomcat.apache.org/tomcat-9.0-doc/config/valve.html#Crawler_Session_Manager_Valve Set the crawler user agent and/or crawler IP appropriately so your load-balancer is treated as a web-crawler and all those health-checks will be associated with a single session. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
