[
https://issues.apache.org/jira/browse/JSPWIKI-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siegfried Goeschl updated JSPWIKI-888:
--------------------------------------
Description:
When running the Portable JSPWiki it is common that some wiki pages are updated
on the file system level, e.g. Dropbox.
JSPWiki currently doesn't doing any checks (as documented) and the default
ehcache.xml does not provide a value for "timeToLiveSeconds" - in this case the
cache entry will never expire.
For the portable scenario a custom ehache.xml will be provided setting
* maxElementsInMemory=128
* timeToLiveSeconds=7200
was:
When running the Portable JSPWiki it is common that some wiki pages are updated
on the file system level, e.g. Dropbox.
JSPWiki currently doesn't doing any checks (as documented) and the default
ehcache.xml does not provide a value for "timeToLiveSeconds" - in this case the
cache entry will never expire.
For the portable scenario a custom ehache.xml will be provided setting
* maxElementsInMemory=100
* timeToLiveSeconds=3600
> Enable cache timeouts for Portable JSPWiki
> ------------------------------------------
>
> Key: JSPWIKI-888
> URL: https://issues.apache.org/jira/browse/JSPWIKI-888
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.10.1
> Reporter: Siegfried Goeschl
> Fix For: 2.10.2
>
>
> When running the Portable JSPWiki it is common that some wiki pages are
> updated on the file system level, e.g. Dropbox.
> JSPWiki currently doesn't doing any checks (as documented) and the default
> ehcache.xml does not provide a value for "timeToLiveSeconds" - in this case
> the cache entry will never expire.
> For the portable scenario a custom ehache.xml will be provided setting
> * maxElementsInMemory=128
> * timeToLiveSeconds=7200
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
