I'm running into the same problem using jbpm-3.1.1, hibernate-3.2.4.SP1 and JBoss 4.0.5.GA. But I'm using this testcode (with a minimum-workflow consisting of a start and an end node) as CMT bean: public void showError() { | | log.info("Request received"); | JbpmContext wfContext = wfConfiguration.createJbpmContext(); | ProcessInstance process = wfContext.newProcessInstance("HelloWorld"); | process.signal(); | | // Session hibernateSession = wfContext.getSession(); | wfContext.close(); | } | As single session bean method called by a servlet. JBoss closes the JDBC connection | 2007-08-17 18:52:20,605 INFO [org.jboss.resource.connectionmanager.CachedConnectionManager] Closing a connection for you. Please close them yourself: org.jboss.resource.adapter.jdbc.WrappedConnection@4f27a3 | java.lang.Throwable: STACKTRACE | at org.jboss.resource.connectionmanager.CachedConnectionManager.registerConnection(CachedConnectionManager.java:290) | But then ... | 2007-08-17 18:52:20,636 INFO [org.jboss.resource.connectionmanager.TxConnectionManager] throwable from unregister connectionjava.lang.IllegalStateException: Trying to return an unknown connection2! org.jboss.resource.adapter.jdbc.WrappedConnection@4f27a3 | at org.jboss.resource.connectionmanager.CachedConnectionManager.unregisterConnection(CachedConnectionManager.java:342) | at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.connectionClosed(TxConnectionManager.java:606) | at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.closeHandle(BaseWrapperManagedConnection.java:266) | at org.jboss.resource.adapter.jdbc.WrappedConnection.close(WrappedConnection.java:129) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.resource.connectionmanager.CachedConnectionManager.closeConnection(CachedConnectionManager.java:529) | at org.jboss.resource.connectionmanager.CachedConnectionManager.access$000(CachedConnectionManager.java:63) | at org.jboss.resource.connectionmanager.CachedConnectionManager$CloseConnectionSynchronization.afterCompletion(CachedConnectionManager.java:607) | at org.jboss.resource.connectionmanager.TransactionSynchronizer.invokeAfter(TransactionSynchronizer.java:301) | at org.jboss.resource.connectionmanager.TransactionSynchronizer.afterCompletion(TransactionSynchronizer.java:271) | at org.jboss.tm.TransactionImpl.doAfterCompletion(TransactionImpl.java:1526) | at org.jboss.tm.TransactionImpl.completeTransaction(TransactionImpl.java:1198) | at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:377) | at org.jboss.ejb.plugins.TxInterceptorCMT.endTransaction(TxInterceptorCMT.java:501) | at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:361) | at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:181) | at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168) | at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) | at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136) | at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648) | at org.jboss.ejb.Container.invoke(Container.java:954) | at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:430) | at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:103) | at $Proxy66.showError(Unknown Source) | at de.telefonica.lich12.jbpmtest.TriggerServlet.doGet(TriggerServlet.java:101) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) | Does anybody know why JBoss is closing the connection just a few milliseconds before JBPM tries it itself? I'm using a clean JBoss 4.0.5.GA with hibernate tree cache as MXBean and JBPM and Hibernate as POJO inside the EAR file (consisting of the small session bean above and the servlet calling that session bean). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075289#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...