This time I used a jboss-cache.jar compiled from the most recent jboss-head out of cvs. You mentioned a change in Region.java and I think you got it. With older jboss-cache.jar's I could always reproduce the dead-lock but never with the new jar in cvs :-)
But there is no change with the repeatable-read scenario (without LRUEviction) and the "loss of money". I changed the testcase: I exchanged all System.out.println's against logging so that you find jboss.cache and testcase log entries mixed (much more better to read). Additionally if there are no outputs to the console the concurrency problems arise more often (due to higher concurrency). I just sent you the log file via email. I'm not sure if you could reproduce this second problem too? Thanks, S. Pohl View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830937#3830937 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830937 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
