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

Thu Jun 12 09:57:34 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBCACHE-131?page=comments#action_12416771 ] 

Manik Surtani commented on JBCACHE-131:
---------------------------------------

Use case does exist, transient state will be persisted to cache loaders IF fetchPersistentState is FALSE.

Needs to be documented in the User Guide AND the FAQs, as well as in a comment in the config files explaining what will happen when fetchPersistentState is false and fetchTransientState is true.

> Cache Loaders (when unshared, and not used with passivation) Should Persist Transient State Upon Startup
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBCACHE-131
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-131
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.2
>            Reporter: Jimmy Wilson
>         Assigned To: Manik Surtani
>            Priority: Minor
>             Fix For: 3.0.0
>
>         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.

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira