https://bz.apache.org/bugzilla/show_bug.cgi?id=69846
Mark Thomas <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from Mark Thomas <[email protected]> --- This is not a Tomcat bug. Tomcat has no control over how or when Kubernetes removes a POD from routing and/or when k8s reroutes requests. The PersistentManager implements Lifecycle so the ability to register a LifecycleListener is already available. Note sessions are persisted between STOPPING and STOPPED. It is not practical for the Tomcat team to document all the available session persistence technologies and all their various options to suit user requirements. Even documenting the popular ones has issues with the range of architectures, options and requirements. I'd suggest that Clustering, the BackupManager and the KubernetesMembershipProvider might be a better solution for you. If you want to explore the options available in Tomcat for this, the users list is the place to ask questions like that. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
