i think i start remembering this problem... the webapp cannot operate with the same hibernate configurations as the jbpm ejbs do. that is, untill the web app isn't refactored to using commands and a command service. webapp needs JTA transactions and the context blocks in the webapp should have transactions enabled. these transactions then result in JTA transactions. that is necessary in case async node execution leads to messages being sent. the jbpm ejbeans need CMT transactions (no transaction demarcation in code). i think the beans might be configured for JTA with transactions enabled, as they will always be inside a CMT method with tx-attribute required. So i think that hibernate will not end the JTA transaction if it didn't created it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025788#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...