2014-05-29 11:58 GMT+04:00 David Rees <dree...@gmail.com>: > I've found that certain applications will no longer invalidate > sessions after upgrading from 7.0.53 to 7.0.54. > > It seems to require clustering to be set up in Tomcat. If it's not set > up, session invalidation works fine. > > So far, I can only trigger it in a webapp that uses Tapestry Spring Security. > > I see a few changes in the changelog related to session invalidate and > clustering, could one of these changes be responsible? >
What are the symptoms? Is there anything unusual in the log files? Is a single web application affected, or it spans several applications (via Single Sign On)? You may consider debugging. http://wiki.apache.org/tomcat/FAQ/Developing#Debugging You may consider simplifying you configuration to build a simple reproduce scenario for a bug report. > Anyone else see the same issue? > Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
