[ http://jira.jboss.com/jira/browse/JBCACHE-38?page=comments#action_12314774 ] Thomas Cherel commented on JBCACHE-38: --------------------------------------
I will be nice if cache data was not cleaned up upon restart. The use case is basically to be able to change the configuration of an exisitng cache without loosing the data contained in the cache. Today, it is not cleaned up, but, for example, the eviction of the JBossCache LRU policy does not work anymore until some kind of node event (like a get or put) is done on the node. > Eviction policy timer starts multiple times if cache is restarted > ----------------------------------------------------------------- > > Key: JBCACHE-38 > URL: http://jira.jboss.com/jira/browse/JBCACHE-38 > Project: JBoss Cache > Type: Bug > Versions: 1.2 > Reporter: Ben Wang > Assignee: Bela Ban > Fix For: 1.2.1 > > Original Estimate: 2 hours > Remaining: 2 hours > > If cache code snippet is like this: > PropertyConfigurator config = new PropertyConfigurator(); > cache.config(); > cache.start(); > cache.stop(); > cache.config(); > cache.start(); > Then the eviction timer will be started twice, for example. This is becuase > the listeners are not clear during stop(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
