anonymous wrote : | | Definitely a limitation. Could you please create a feature request in JIRA for this and vote for it? | If i find out how or where to do this i will ;). anonymous wrote : | What could be your problem is how often your eviction thread kicks in. If you have enough memory to deal with temporary spikes before the eviction thread clears down unused nodes, I'd set this not to run too frequently. | Currently running every 5 seconds, will set it for a longer time period. Can you set the "wakeUpIntervalSeconds" on a region basis or is it a global cache setting?? anonymous wrote : | I don't think it is replication, although you could tune it by using a ReplicationQueue (by default, even async replication happens immediately; the caller thread just doesn't wait for the response). See the user guide/sample configs for how to use the ReplicationQueue to defer this; it can be triggered either by time or size. | Hmmm im not sure we are talking about the same async, I´m talking about the asynch mode with the cacheloader i.e JDBCCacheLoader nothing to do with replication. Ive actually set this cache as LOCAL so i have no replication going on what so ever. What I was asking was is there any way to get the asynch buffer for the JDBCCaheLoader to run more often/quicker to clear the buffer as quick as possible?? Reason i ask is that when i run say 5,000 writes and stop, i check the the DB to see how many records are written and i can see that over the space of one to three,four minutes it eventually will write all records in the DB. But it is this 3-4 minutes time lag that worries me, in production it wont get this 3-4 min break. Maybe it actually is running as fast as possible to clear the buffer but due to the fact it is writing images it actually takes this long!! anonymous wrote : | Also, if you are using the cache directly (i.e., packaged in your webapp or ear), you could even use 2.0.0/2.1.0 with JBoss AS 4.x. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAsCompatibility | Thanks for the info, I already tried 4.2.X with JBossCache 2.0 and tried deploying as an MBean, this is a while back now, but i remember i did run into problems trying to deploy it as an MBean and when i did get it to work none of the statistics were getting updated in jmx-console. So was kind of put off the combination of 4.2.x with JbossCache 2.0 but i might have to venture back with this combination! Thanks Manik, LL View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122514#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...