File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Struts and the fly likes Logout and Tomcat Manager application session tracking Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Frameworks » Struts
Bookmark "Logout and Tomcat Manager application session tracking" Watch "Logout and Tomcat Manager application session tracking" New topic

Logout and Tomcat Manager application session tracking

Ranch Hand

Joined: Mar 11, 2003
Posts: 33

My application is using Tomcat and Struts framework. The problem I found is the session invalidation and Tomcat Manager Application's session tracking number conflict (or confusion). When user logs on to our application, I see the number of session in Tomcat manager application gets increased as expected; however, it did not get decreased as user logged out. This is what I do in the LogoutAction:

However, if I call in the logout.jsp (kind of redundent, since LogoutAction has already invalidate the user's current session), then the session number in Tomcat manager application will get decreased, proving the user did has already logged out. Why is this? How does Tomcat tracks application's session number? Or the session number did not get decreased because actually another new session has been created again in the logout.jsp? If this is the case, how should I address this problem without putting JAVA code (to invalidate session) in jsp page, or just ignore the Tomcat session number as long as I do proper session invalidion in logout action?

Thanks very much for your help!
I agree. Here's the link:
subject: Logout and Tomcat Manager application session tracking
Similar Threads
Basic page logout design
Session problem in Struts and Tomcat
How to handle back button caching
How to disabel the back and forward after session is invalidated