Thanks for the response vzilka,
Our JSPs for the application are stored in tomcat/webapps/dir/app, and tomcat/webapps/dir contains the entire application. I tried placing the code in the web.xml file inside tomcat/webapps/dir/web-inf
vzilka, could you explain what you mean by:
"Theortically the session should be invalidated, but Tomcat may decide it has enough memory and won't run the thread that destroys the sessions."
Do you mean that tomcat may not run session.invalidate() when the session times out?
-or-
Do you mean that session.invalidate() will be run, but the garbage collection may not collect the un-referenced memory right away?
Also, does session.invalidate() just de-reference all of the objects associated with that session?
As long as the memory is unreferenced, I think that I can put a little trust in the garbage collector to someday pick up the trash when the app needs the extra memory.
If tomcat just doesn't invalidate the session at all if it doesn't have to, then is there a way to find out which session has timed out and then manually invalidate it?
Thanks for any help you guys/gals can give.
Nathan @ AK
Main Topics
Browse All Topics





by: vzilkaPosted on 2004-02-10 at 13:23:46ID: 10326441
I don't understand what is the app directory. -INF
I think your web.xml file should be in TOMCAT/WEBAPPS/DIR/WEB-INF
or, if you do not use the auto deploy features of TOMCAT but wrote a context in the server.xml file, TOMCAT/WEBAPPS/DIR/APP/WEB
Theortically the session should be invalidated, but Tomcat may decide it has enough memory and won't run the thread that destroys the sessions.