I have been able to recreate this. I will soon add a modified version of your test (modified to fit our test fwk) to our unit test suite. Just as an FYI, this fails on branch 2.1.X but not on trunk (soon-to-be 2.2.0). I'll add a more formal analysis about this issue soon, but for now, see: JBCACHE-1320, which is a feature added in 2.2.0 which probably fixed this issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146578#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...