For the EJB3 SFSB cache I do something similar to what Sancheski describes. I realize now
it works OK because that cache has useRegionBasedMarshalling=true, so even though the
cache is started the region is empty when I programatically add the eviction region
config. That's kind of a fortunate fluke though; being able to programatically add
the region without requiring region-based marshalling would be nice. Without region-based
marshalling, there could be pre-existing nodes.
I wouldn't worry about the # of preexisting nodes exceeding maxNodes issue. The first
time the eviction thread runs, it will take care of it; it's the job of eviction
processing to worry about that.
Re: every pre-existing node having the same timestamp in the eviction queue, oh well.
Don't see any way around that without storing a creation timestamp in each node, which
IMO is big time overkill. The main thing is making sure the policy knows about all nodes.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4149213#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...