On Mon, 2008-10-20 at 08:53 -0700, rainer wrote:
> Thx for the upgrade hint, but - is caching in 3.6.1 not stable? 

It is always easier to verify and debug any issue against latest release
then against some older version. Also when running into issue, if you
are not using latest version, chances are that someone else already
found the issue so you should either try to reproduce the issue with
latest version or at the very least check the jira for any new issues
reported since the release data of the version you are using.

And as a matter of fact, brief look at the issues resolved after 3.6.1
revealed this one: http://jira.magnolia-cms.com/browse/MAGNOLIA-2346
which might explain your problem, and why I do not see it on 3.6.3

Cheers,
Jan

> 
> @Works fine for me. Are you sure that you are NOT testing on author with
> magnolia.develop = true ? 
> 
> Yes, i am.
> 
> @Or that you have NOT disabled cache filter
> previously?
> 
> Yes, i am. The cache filter is in the chain - and set to:
> 
> 1. cacheConfigurationName = default
> 2. class = info.magnolia.module.cache.filter.CacheFilter
> 
> I'll try JConsole tomorrow...
> 
> thx
> 
> 
> 
> Magnolia - User mailing list-2 wrote:
> > 
> > On Mon, 2008-10-20 at 06:44 -0700, rainer wrote:
> >> Hi list,
> >> 
> >> i am just taking a look the caching in 3.6.1. Maybe you can help me
> >> understand ;)
> > 
> > You should upgrade to 3.6.3.
> > 
> >> i saw that the default setting holds 10000 cache entries in-memory...
> >> 
> >> In 3.5 i could take a look in the "cache" folder - there the page
> >> structure
> >> could be found - and i saw the files that were served. 
> >> 
> >> How can i see, that the cache is working - and which pages are cached?
> >> Right
> >> now i can only find two 0 KB files in the cache folder: "default.data"
> >> and
> >> "default.index".
> > 
> > Since 3.6 Magnolia is using ehCache to cache the content on the server
> > and those 2 files represent ehCache data store, you won't be able to see
> > the page structure in file system any more. You can enable jmx and use
> > jconsole to observe the cache.
> > 
> >> 
> >> Even if i say: "maxElementsInMemory = 1" nothing appears in the cache
> >> directory (if i request many pages afterwards). 
> > 
> > Works fine for me. Are you sure that you are NOT testing on author with
> > magnolia.develop = true ? Or that you have NOT disabled cache filter
> > previously?
> > Please use jconsole and look at attributes of
> > net.sf.ehcache.CacheManager to make sure that there are some hits on the
> > cache. If there are hits you should see the default.data file in cache
> > directory to grow up.
> > 
> > Cheers,
> > Jan
> > 
> > 
> > ----------------------------------------------------------------
> > for list details see
> > http://www.magnolia-cms.com/home/community/mailing-lists.html
> > ----------------------------------------------------------------
> > 
> > 
> 
-- 
Best regards,

Jan Haderka
Magnolia International Ltd.

----------------------------------------------------------------------
[EMAIL PROTECTED]                http://www.magnolia-cms.com
Magnolia®  - Simple Open Source Content Management
----------------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
----------------------------------------------------------------

Reply via email to