[
https://issues.apache.org/jira/browse/WICKET-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842575#comment-17842575
]
Martin Tzvetanov Grigorov commented on WICKET-7108:
---------------------------------------------------
If Tomcat does not send us a notification about invalidating http sessions then
there is no way to know what to delete.
The provided information is not enough to do a deeper investigation...
What does it mean "tomcat went down, index file was not saved" ?
Define "went down"! Is this a normal stop or a kill ?
What is `index file" ?
> Wicket file storage bloating
> ----------------------------
>
> Key: WICKET-7108
> URL: https://issues.apache.org/jira/browse/WICKET-7108
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 10.0.0
> Reporter: Viliam Repan
> Priority: Major
>
> DiskPageStore doesn't cleanup old/invalid session data. AFAIK there are two
> scenarios when it forgets about content in wicket file store folder:
> * normal restart of tomcat, index was saved, however all sessions that were
> invalidated by restart - files for them will never be cleaned up.
> * tomcat went down, index file was not saved - whole wicket file store now
> contains files that will never be cleaned up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
