There are few more things to be done: OptimisticTreeCacheProvider looks for treecache.xml in classpath and currently this is not configurable. So, either we need to have a similar implementation in portal that can read TreeCache definition from jboss-service.xml or some configurable locaton OR we need to create org.jboss.portal.jems.hibernate.JBossOptimisticTreeCacheProvider similar to org.jboss.portal.jems.hibernate.JBossTreeCacheProvider so that it looks for already deployed TreeCache mbean (the one defined through treecache.xml). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101418#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...