We get dangling cache files. I have the sessions set to expire in 1 hour. I check one of my servers and i see cache files from over a week old. This could of only have occurred because of the multiple restarts. Maybe its a bad timing where the HttpSessionBindingListener does not receive a notification.
I figured the DiskPageStore probably kept a map of cache files. I those references were kept in memory, there be a separate thread that runs and grabs all file cache names in the file store (basically the JSESSIONIDs) and compare that to the references in the map to see what is a valid cache file. I suppose my assumptions are wrong. Johan Compagner wrote: > >> >> >> 1) Shall we file a Jira for a enhancement to the DiskPageStore which >> would >> be a cleanup of any dangling cache files not part of the current >> DiskPageStore instance? > > > and which are dangling?? > How do you know that? If i stop tomcat (even in development mode) > and i restart again nothing is dangling!! All the session are still there > and are still > using the page store. > > And from top of my head there is no api to get all the current session > id's > from > an instance when the instance does start up.. > > So as long as we can't do that, we can't delete files because we have no > idea if the sessions are really gone or not. > I guess a seperate cron job can clean up the files in that dir if they are > really old? > > johan > > -- View this message in context: http://www.nabble.com/How-To-Change-Page-Store-Size-in-DiskPageStore--tf4768072.html#a13658369 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
