Alejandro Guizar [http://community.jboss.org/people/alex.guizar%40jboss.com] replied to the discussion "Close ProcessEngine upon BPM console undeployment" To view the discussion, visit: http://community.jboss.org/message/550290#550290 -------------------------------------------------------------- The process engine needs to be closed by the module that created it. In JBoss AS this is already covered since jBPM is deployed as a service. The JbpmService bean correctly closes the engine on stop. In Tomcat the situation is more complicated. Because it lacks the notion of services, the jbpm-console app creates the process engine itself. The  engine cannot be managed by a separate module and shared via JNDI because Tomcat provides a read-only initial context. In fact, the situation is aggravated due to Configuration.getProcessEngine() returning a shared instance. I take this method to be a formal equivalent of the http://docs.jboss.org/hibernate/stable/core/reference/en/html/tutorial.ht... HibernateUtil class in standalone environments. Unfortunately, it is tempting to call this method from within containers, where it is totally insane. The engine becomes reachable from the entire VM and there is no clear point at which it can be closed. This would be an option if the shared ProcessEngine could be closed on servlet context destruction, which is not possible as said before. If the servlet context listener built its own unshared engine on initialization, it could close it on destruction. Unfortunately such an engine is unreachable for the console integration components. In a typical web app it would be set  as an attribute of the servlet context, but the servlet context itself is unreachable as well. One promising alternative I want to investigate is the Tomcat http://tomcat.apache.org/tomcat-6.0-doc/jndi-resources-howto.html#Adding%... custom resource factory. There is http://community.jboss.org/wiki/UsingJNDI-boundSessionFactorywithTomcat41 prior art in this direction involving the Hibernate session factory. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/550290#550290] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]