Question regarding configurable cache timeout

[Siegfried Goeschl <sg...@gmx.at>]

Hi folks,

when running the Portable JSPWiki it is common that some wiki pages are updated on the file system level, e.g. Dropbox.

JSPWiki does currently not doing any checks (as documented) but the caches uses a "0" setting (infinite) for

* timeToLiveSeconds
* timeToIdleSeconds

In other words - JSPWiki will NEVER pick up any "behind-the-back" changes until you restart it.

When looking at “CachingProvider” it seems that the caches are created by the code but the following comment 

/** The capacity of the caches, if you want something else, tweak ehcache.xml. */
public static final int   DEFAULT_CACHECAPACITY   = 1000; // Good most wikis

indicates that I can tinker with the “ehcache.xml”? 

Not sure how this two things connect  - any ideas :-)

Thanks in advance

Siegfried Goeschl

Re: Question regarding configurable cache timeout

[Siegfried Goeschl <sg...@gmx.at>]

Okay - found the answer - the caches are created based on the ehcache.xml

Sorry for the noise

Siegfried Goeschl

> On 25 Jun 2015, at 23:22, Siegfried Goeschl <sg...@gmx.at> wrote:
> 
> Hi folks,
> 
> when running the Portable JSPWiki it is common that some wiki pages are updated on the file system level, e.g. Dropbox.
> 
> JSPWiki does currently not doing any checks (as documented) but the caches uses a "0" setting (infinite) for
> 
> * timeToLiveSeconds
> * timeToIdleSeconds
> 
> In other words - JSPWiki will NEVER pick up any "behind-the-back" changes until you restart it.
> 
> When looking at “CachingProvider” it seems that the caches are created by the code but the following comment 
> 
> /** The capacity of the caches, if you want something else, tweak ehcache.xml. */
> public static final int   DEFAULT_CACHECAPACITY   = 1000; // Good most wikis
> 
> indicates that I can tinker with the “ehcache.xml”? 
> 
> Not sure how this two things connect  - any ideas :-)
> 
> Thanks in advance
> 
> Siegfried Goeschl
> 
>