If you are not caching queries, that's good. We're on the same page on your config, which can now be applied to the CMS cache. If that and use_query_cache=false don't resolve your issue there's either something I'm missing in how JBC handles invalidation in the Hibernate "put" use case (db read + cache write) or your testing is doing a really high number of entity creations/updates (which isn't going to scale). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165951#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...