Hi, we have this annoying problem that although Tomcat workers are set to DIS state in mod_jk, there are new connections being opened. This prevents us from "idle down" Tomcats in a timely fashion. This hurts when a restart is needed. While our empathy for human clients is pretty limited, we care a lot about our automated workloads :-)
Our setup: Apache 2.4.x frontend -> mod_jk(1.2.42) balancer, sticky sessions -> a bunch of Tomcat 7 (yes I know. Oldie but Goldie :-) workers. As far as I understand, the problem arises with HTTP(S) clients that cache the session cookies. If such a client tries to open a new connection to the backend, the old cookie passes to a DIS worker even if it is no longer valid on the Tomcat side. Tomcat/Application then sees that the cookie is not valid and doles out a new cookie which then allows the new connection to be established. My idea is now to delete existing session cookies for certain request pattern on the Apache frontend. If it works, it should force mod_jk to a new ACT Tomcat. But I am nor really fond of messing with the Apache configuration, as the reason lies on the mod_jk/Tomcat side. So if anybody has another suggestion I would love to hear it. Before I forget, changing the application itself is not an option. TIA Martin -- ------------------------------------------------------ Martin Knoblauch email: k n o b i AT knobisoft DOT de www: http://www.knobisoft.de
