[jboss-jira] [JBoss JIRA] Resolved: (JBCACHE-131) Cache Loaders (when unshared, and not used with passivation) Should Persist Transient State Upon Startup

Cache Loaders (when unshared, and not used with passivation) Should Persist Transient State Upon Startup -------------------------------------------------------------------------------------------------------- Key: JBCACHE-131 URL: https://jira.jboss.org/jira/browse/JBCACHE-131 Project: JBoss Cache Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Cache loaders Affects Versions: 1.2.2 Reporter: Jimmy Wilson Assignee: Manik Surtani Fix For: 3.0.0.BETA1, 3.0.0.GA Attachments: TreeCache.zip Given the following single, unshared cache loader use case in the TreeCache documentation: "This is a similar case as the previous one, but here only one node in the cluster interacts with a backend store via its CacheLoader. All other nodes perform in-memory replication. A use case for this is HTTP session replication, where all nodes replicate sessions in-memory, and - in addition - one node saves the sessions to a persistent backend store" A cache with attached cache loader should persist the transient state of the cache to disk upon startup in order to maintain cache recoverability. I have modified TreeCache to handle this situation, and I will attach the modified code to this issue.