[jboss-jira] [JBoss JIRA] Closed: (JBCLUSTER-242) Use CacheLoader config's purgeOnStartup to control whether cache is cleared at start/stop

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBCLUSTER-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry closed JBCLUSTER-242.
--------------------------------------

    Resolution: Done


> Use CacheLoader config's purgeOnStartup to control whether cache is cleared at start/stop
> -----------------------------------------------------------------------------------------
>
>                 Key: JBCLUSTER-242
>                 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-242
>             Project: JBoss Clustering
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: HA-Server-Cache-JBC
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Minor
>             Fix For: HA-Server-Cache-JBC 2.1.0.GA 
>
>
> Revisit JBAS-5627.  The analysis in the subtasks under that JIRA is sound, but by hardcoding that the persistent store is cleared if buddy replication or region based marshalling is used, we leave no way out for things like development environments where people want flexibility. However, the standard configs used in the AS all set the JBC purgeOnStartup flag to true, so rather than hard-coding behavior we can check that flag. People who want to be able to read persisted sessions off disk after restart can set the flag to "false".
> Ideally, this behavior would be controlled via jboss-web.xml rather than a fairly obscure JBC config, but for now this is a simple improvement.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira