I've setup a Seam managed jbpmsession nearly identical to the demo. But, I'm constantly getting this in the logs:
INFO [ConnectionManager] Skipping aggresive-release due to open resources on batcher
I know this comes from hibernate, but it didn't start showing up until I started working with seam + jbpm. Any ideas how I can avoid this? It's INFO, but it doesn't seem good. Here's my pertinent hibernate config for jbpm:
.... <property name="hibernate.dialect">org.hibernate.dialect.HSQLDialect</property> <property name="hibernate.show_sql">false</property> <property name="hibernate.hbm2ddl.auto">update</property> <property name="hibernate.cache.provider_class">org.hibernate.cache.HashtableCacheProvider</property> <!-- managed-env properties --> <property name="connection.datasource">java:/jbpmDatasource</property> <property name="transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property> <property name="transaction.manager_lookup_class">org.hibernate.transaction.JBossTransactionManagerLookup</property> <property name="jta.UserTransaction">java:comp/UserTransaction</property> ....
Essentially this means that you (or jBPM perhaps) are using either a Query.iterate() or Query.scroll(). Both of these methods hold open resources (result-sets) on the session; thus the session is not able to aggressively release the jdbc connection.