Another path to investigate further is associating the jBPM Environment to the JTA transaction (JBPM-2197). Suppose a user manages a JTA tx with an EJB method. Inside that method there are 3 subsequent invocations to the jBPM services. In the current configuration, the EnvironmentInterceptor will create 3 separate environments. But we could also do just like hibernate and seam in that case. During interception of the first method invocation, create a new Environment and then associate it to the JTA transaction and close it in the beforeCompletion of a Synchronization. Then the 2 subsequent invocations within the same TX could find and leverage that environment. Nice proposal, but we need to figure out a way to have the environment created/closed after/before the Hibernate session is created/closed. Otherwise we will hit the problem with Synchronizations we had in jBPM 3. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227080#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...