-
1. Re: Eviction Policy Config not working
lords_diakonos Jul 28, 2008 3:04 PM (in response to lords_diakonos)For what it is worth now I changed the _default_ region to maxNodes = 1 and it still caches more.
I do have the 1
so it should be firing i think
Anybody know what is happening? -
2. Re: Eviction Policy Config not working
manik Aug 4, 2008 1:04 PM (in response to lords_diakonos)In your logs - do you see the eviction thread kicking in and attempting to evict stuff every 3 seconds?
-
3. Re: Eviction Policy Config not working
lords_diakonos Aug 4, 2008 1:29 PM (in response to lords_diakonos)Well it was firing. I think the issue though I am testing now is that I thought the objects within the FQN were nodes. They don't seem to be though. So I had a FQN which I put a bunch of objects inside. It is all one node though. I was confused here.
My question would now be what is the best way to handle this? Do I need a separate node for every object? That seems kind of dumb as all my nodes and keys would be the same. -
4. Re: Eviction Policy Config not working
manik Aug 4, 2008 4:35 PM (in response to lords_diakonos)A lot of people do use a separate node for each object - and hence JBCACHE-1082.
Another approach is logical groupings. E.g., if you store information about a person, you could store name, age and postcode on the same node.