True, the docs are not completely matching the 3.2 version, as the paths mentioned in this chapter still refer to the 3.1.x starters kit. But in general, the process of switching the DB backend is still roughly the same. Now, back to your initial issue. I'm wondering if your config changes are really getting picked up. In the server.log you should see similar messages: 5785:2008-03-11 13:09:36,054 INFO [org.hibernate.cfg.Configuration] configuring from resource: hibernate.cfg.xml | 5786:2008-03-11 13:09:36,054 INFO [org.hibernate.cfg.Configuration] Configuration resource: hibernate.cfg.xml | 5790:2008-03-11 13:09:36,165 DEBUG [org.hibernate.cfg.Configuration] hibernate.dialect=org.hibernate.dialect.PostgreSQLDialect | 5791:2008-03-11 13:09:36,165 DEBUG [org.hibernate.cfg.Configuration] hibernate.cache.provider_class=org.hibernate.cache.HashtableCacheProvider | 5792:2008-03-11 13:09:36,165 DEBUG [org.hibernate.cfg.Configuration] hibernate.connection.datasource=java:/JbpmDS | of course in your case for mysql. Also, check if you have multiple hibernate.cfg.xml files somewhere in your deployment, also check inside archives as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135586#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...