"Henrik Nyberg" wrote : | | Settings for the cache are: | * Asynchronous replication (replAsync-service.xml out of the box with the suggested modification for windows, i.e. loopback = true). | * no transactions (IsolationLevel.NONE) |
Have no transactions is very bad, as the cache replicates after *every single* modification. If you cannot be forced to use transactions, at least enable queueing, so modifications are replicated in batches. Also, if you stress-test the cache, you might be better off using the fc-fast config from JGroups/conf. If this doesn't solve your problems, please open a bug report on JIRA (http://jira.jboss.com/jira/browse/JBCACHE). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866788#3866788 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866788 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
