Okay, I have traced this down and it has nothing to do with JBCACHE-1320. It has been fixed in trunk as a matter of course in refactoring some classes. It is fixed in Branch 2.1.X as well and will be released with 2.1.1, but there is a workaround for 2.1.0.GA as well - see JBCACHE-1330. Do let me know if the workaround solves your problem! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146772#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...