You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Johan Compagner (JIRA)" <ji...@apache.org> on 2009/07/08 10:54:14 UTC

[jira] Commented: (WICKET-2357) (follow-up of WICKET-1158) DiskPageStore does not cleanup cache files after Web container restarts

    [ https://issues.apache.org/jira/browse/WICKET-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728570#action_12728570 ] 

Johan Compagner commented on WICKET-2357:
-----------------------------------------

1 solution would be to not kill tomcat..
but always do a nice shutdown :)

> (follow-up of WICKET-1158) DiskPageStore does not cleanup cache files after Web container restarts
> --------------------------------------------------------------------------------------------------
>
>                 Key: WICKET-2357
>                 URL: https://issues.apache.org/jira/browse/WICKET-2357
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>            Reporter: Peter Ertl
>         Attachments: WICKET-2357-1_3.patch, WICKET-2357-1_4.patch
>
>
> in WICKET-1158 there was some talk about cleaning up stale pagemap files of DiskPageStore on non-graceful container restarts (e.g. when doing kill -9). Last comment stated this issue will be fixed when related WICKET-1161 is fixed. However WICKET-1161 is fixed now and stale files are not cleaned up on container restarts where the container was not shut down gracefully.
> Especially on high-volume sites lots of files could be left behind and as wicket creates the files it should also clean them up again. I could imagine some kind of (optional) low-priority cleanup background thread that removes files having a lastModifiedTime > threshold value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.