[
http://jira.jboss.com/jira/browse/EJBTHREE-500?page=all ]
Ben Wang resolved EJBTHREE-500.
-------------------------------
Fix Version/s: EJB 3.0 RC9 - FD
Resolution: Done
I have ported the solution both to 4.0 and head. The JBoss Cache version needed is 1.4.
Basically, the only change is that we are using the passivation feature in JBC now
(ejb3-clustered-stateful-service.xml).
User can still tune the eviction thread wakeUpIntervalSeconds and also the location of the
FileCacheLoader.
Additionally, if the bean is currently in use (and inactive for a while), we won't
passivate/evict it untill it is no longer in use.
The rest of the configuration should stay the same.
Use JBossCache passivation feature for clustered ejb3 SFSB
----------------------------------------------------------
Key: EJBTHREE-500
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-500
Project: EJB 3.0
Issue Type: Task
Components: Clustering
Reporter: Ben Wang
Assigned To: Ben Wang
Fix For: EJB 3.0 RC9 - FD
Original Estimate: 1 week, 1 day
Time Spent: 1 week
Remaining Estimate: 1 day
Currently the clustered sfsb uses its own passivation implmentation because JBossCache
didn't offer that previously. However, now that it has this feature, we should
refactor to use that. There is a corresonding Forum post for this discussion.
--
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