-
1. Re: JBoss Cache able to set cache size limit based on memory
I found the answer to my first question on these forums here:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=61990
I am still trying to find out how Jboss cache handles locking of the cache when a load for a key is in progress.
As well as how JBoss Cache handles these as well:
1. duplicate requests
2. load on start up option
3. warm cache on start up option
4. turning off of distributed cache features such as multicasting -
2. Re: JBoss Cache able to set cache size limit based on memory
// Q: Is JBoss Cache able to set cache size limit based on
// memory usage instead of quantity of objects?
A: Not yet, but it is on the roadmap: http://jira.jboss.com/jira/browse/JBCACHE-11
// Q: Also, does anyone know how JBoss Cache handles
// locking of the cache when a load for a key is in
// progress?
The node will be locked -
3. Re: JBoss Cache able to set cache size limit based on memory
Thanks Bela!
Do you know how JBoss Cache handles or has the ability for these as well?
1. duplicate requests
2. load on start up option
3. warm cache on start up option
4. turning off of distributed cache features such as multicasting
Best Regards,
Sean Gildea -
4. Re: JBoss Cache able to set cache size limit based on memory
"sean_gildea" wrote:
Thanks Bela!
Do you know how JBoss Cache handles or has the ability for these as well?
1. duplicate requests
2. load on start up option
3. warm cache on start up option
4. turning off of distributed cache features such as multicasting
Best Regards,
Sean Gildea
#1 JGroups
#2 preload attribute in XML file
#3 same as #2
#4 JGroups