[
http://jira.jboss.com/jira/browse/EJBTHREE-915?page=comments#action_12356349 ]
Brian Stansberry commented on EJBTHREE-915:
-------------------------------------------
Re: the "open question" above, scotto reports he saw the problem when restarting
after hard killing the JBoss process. StatefulTreeCache.stop() is not called in a hard
kill, hence old nodes are left on disk.
Clustered SFSB cache should not preload from the cache loader
-------------------------------------------------------------
Key: EJBTHREE-915
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-915
Project: EJB 3.0
Issue Type: Bug
Components: Clustering
Affects Versions: AS 4.2.0 CR1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: AS 4.2.0 CR2
Preloading the cache is causing conflicts with region activation, since the preload
happens before the region is activated (and thus pollutes the in memory cache, causing the
activation to fail.) In any case, preloading doesn't make sense for the SFSB cache;
any state on disk would be passivated sessions that had been in use on another node; they
are only useful in memory if the client fails over. No point aggressively bringing them
into memory.
Fix is to remove the <preload>/</preload> element from the
ejb3-clustered-sfsbcache-service.xml file.
An open question is why there are nodes to be preloaded. StatefulTreeCache.stop() should
be causing them to be deleted, and starting the cache shouldn't be bringing over any
state transfer. Perhaps some file lock is preventing the node deletion?
--
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