Change By: Roman Kovařík (05/Feb/15 3:08 PM)
Summary: Investigate  possibility of  runtime reconfiguration
Description: Currently we call {{ info CacheManager . magnolia.module.cache.ehcache.EhCacheFactory#start shutdown() }}  which deregister it and the content of living caches is lost (probably because the persistence is not supported in non-re edition).

If we want to keep live caches
:
# We  register  can't call  {{ CacheManager shutdown }}  with proper name since MGNLCACHE-60  on restart .  Because of this we cannot register a new manager with updated configuration ({{net.sf.ehcache.management.ManagementService#registerMBeans}}).  
# At least some of the properties should be configurable at runtime (see {{net.sf.ehcache.config.Configuration.DynamicProperty}}). The change of {{defaultCacheConfiguration}} is enough for us. 
Not sure how to change the configuration of an existing manager. We could test:
- {{cacheManager = CacheManager.create(cfg);}}
- {{cacheManager.getConfiguration().setDefaultCacheConfiguration()}}
- ...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to