https://bz.apache.org/bugzilla/show_bug.cgi?id=64051
--- Comment #14 from Mark Thomas <ma...@apache.org> --- I can recreate this with a simple 3 node cluster (no status worker, no standby worker) and a JSP that shows the current node (host name) without creating a session. The session cookie is created on the first request and then mod_jk keeps it sticky to which ever node is used. If that node is then stopped, mod_jk fails over to one of the other nodes but the session is not updated. I have a patch for this that fixes the problem for me. It does indeed appear that s->sticky was being set to true when it should not have been. I'll attach the patch shortly. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
