topic Re: Activit DB Connection pool leak on WL in Alfresco Archive

Activit DB Connection pool leak on WL

schitale — Wed, 25 Sep 2013 19:22:14 GMT

I didnt get any answer on activiti engine forum for this:I see this multiple times in the WL log:ACTIVITI_DB_POOL is the conn pool we use to connect to activit engine.<Sep 24, 2013 7:39:10 PM EDT> <Notice> <Stdout> <BEA-000000> <Returning ALBPM JDBC Connection ….> <S

Re: Activit DB Connection pool leak on WL

schitale — Wed, 25 Sep 2013 19:23:17 GMT

* I see this multiple times in the WL log:

<code>
<Sep 24, 2013 7:39:10 PM EDT> <Notice> <Stdout> <BEA-000000> <Returning ALBPM JDBC Connection ….>
<Sep 24, 2013 7:39:23 PM EDT> <Warning> <JDBC> <BEA-001153> <Forcibly releasing inactive connection "weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection@17a3db" back into the connection pool "Activiti_S300_ACTIVITI_DB_POOL_V1", currently reserved by: java.lang.Exception
        at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:308)
        at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:314)
        at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:292)
        at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:425)

</code>

Re: Activit DB Connection pool leak on WL

schitale — Wed, 25 Sep 2013 19:24:16 GMT

* Sep 24, 2013 7:39:23 PM EDT Warning JDBC BEA-001153Forcibly releasing inactive connection "weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection@17a3db" back into the connection pool "ACTIVITI_DB_POOL", currently reserved by: java.lang.Exception
        at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:308)
        at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:314)
        at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:292)
        at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:425)

Re: Activit DB Connection pool leak on WL

frederikherema1 — Wed, 02 Oct 2013 07:55:54 GMT

What process-engine configuration are you using? Seems that the activity interceptors are closing the connections manually, instead of having the transaction-provider handle this. Depending on your ProcessEngineCOnfiguration subclass, this shouldn't happen…

Re: Activit DB Connection pool leak on WL

melentye — Wed, 02 Oct 2013 08:20:44 GMT

Hello schitale,

what are your logging/profiling settings that allow you to see second exception? What is the value of "Inactive Connection Timeout" setting in "advanced" part of ACTIVITI_DB_POOL data source configuration in WL domain console?

We have noticed connection leak on Weblogic 12c with Activiti 5.12.1 as well but its not logged or reported anywhere unless we switch on Data Source Profile Log - we just see that over time we run out of connections rather quickly on highly loaded system

thanks,
Andrey

Re: Activit DB Connection pool leak on WL

melentye — Wed, 02 Oct 2013 15:30:09 GMT

@frederikheremans, just in case: we're facing similar (or same) issue and we use JtaProcessEngineConfiguration and in activiti.cfg.xml we're pointing to weblogic TransactionManager JNDI name

Re: Activit DB Connection pool leak on WL

schitale — Wed, 02 Oct 2013 21:03:26 GMT

This is my config xml.

<jee:jndi-lookup id="activitiDataSource" jndi-name="ACTIVITI_DB_POOL_V1"/>

<bean id="transactionManager"
class="org.springframework.transaction.jta.JtaTransactionManager">
<!– property name="dataSource" ref="activitiDataSource" / –>
</bean>

<bean id="bpmConnectionParams" class="com.xxx.activiti.identity.BpmConnectionParams" />

   <bean id="springJobExecutor" class="org.activiti.spring.components.jobexecutor.SpringJobExecutor">
<property name="taskExecutor">
   <bean class="org.springframework.scheduling.commonj.WorkManagerTaskExecutor">
    <property name="workManagerName" value="wm/ActivitiWM" />
    <property name="resourceRef" value="true" />
   </bean>
</property>
</bean>

<bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
<property name="dataSource" ref="activitiDataSource" />
<property name="transactionManager" ref="transactionManager" />
<property name="databaseSchemaUpdate" value="true" />
<property name="mailServerHost" value="localhost" />
<property name="mailServerPort" value="5025" />

<property name="jobExecutor" ref="springJobExecutor" />
<property name="jobExecutorActivate" value="true" />

<!– NONE("none"),
ACTIVITY("activity"),
AUDIT("audit"),
FULL("full"); –>
<property name="history" value="none" />

<property name="customSessionFactories">
   <list>
    <bean class="com.xxx.activiti.identity.BpmGroupManagerFactory">
     <constructor-arg ref="bpmConnectionParams" />
    </bean>
    <bean class="com.xxx.activiti.identity.BpmUserManagerFactory">
     <constructor-arg ref="bpmConnectionParams" />
    </bean>
   </list>
</property>
</bean>

<bean id="processEngine" class="org.activiti.spring.ProcessEngineFactoryBean">
<property name="processEngineConfiguration" ref="processEngineConfiguration" />
</bean>

Re: Activit DB Connection pool leak on WL

schitale — Wed, 02 Oct 2013 21:13:22 GMT

One more follow up.

We have fairly long running WS calls . ( > 60 sec and we are trying to fix it.)

I've set "Inactive Connection Timeout" to 0 in my dev env and for now it is not showing any problem obviously.

Earlier that value was 60.

I've tested probably 30/40 request after that and I've not seen any thread hogging up connections.

I'm not sure, but my understanding is (and I may be wrong) that since my WS calls are more that 60s the transaction started by BPM is taken back resulting in:

* Sep 24, 2013 7:39:23 PM EDT Warning JDBC BEA-001153Forcibly releasing inactive connection "weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_T4CConnection@17a3db" back into the connection pool "ACTIVITI_DB_POOL", currently reserved by: java.lang.Exception

When the WS call returns and process instance completes, the connection is closed for the activiti thread.

I may be mistaken, please correct me.

Re: Activit DB Connection pool leak on WL

frederikherema1 — Thu, 03 Oct 2013 08:05:04 GMT

Yes, that makes sense… If you expect long-running operations, make sure your transaction-timeout is high enough. Offcourse, long-running transactions is not always a good idea. Another approach whould be to use camel (for example) for the long-running work,without keeping a transaction in activiti open. Or if not using camel, use a receive-task and trigger the long-running work in another system/app. once that app completes the operation, "signal" activiti, providing the result of the operation. Than, activiti can continue the process

Re: Activit DB Connection pool leak on WL

arunpmohan — Tue, 14 Jan 2014 22:43:50 GMT

I still see connection leak on activiti 5.13 on weblogic 10.3.5.
Is there any fix in activiti 5.14 for connection leaks?

Re: Activit DB Connection pool leak on WL

frederikherema1 — Wed, 15 Jan 2014 09:01:14 GMT

You can use any datasource/pool you want with activiti, nothing is done in activiti to fix any leaks, as this is not in the scope of the engine. The engine just gets connections from the pool and releases them…

Re: Activit DB Connection pool leak on WL

viresh_managool — Fri, 18 Apr 2014 09:08:31 GMT

hello,

Even we are facing same issue with respect to oracle DB. We have configured the following settings in hibernate.cfg.xml, but still we are facing connections leak.

<code>
<property name="hibernate.c3p0.min_size">5</property>
<property name="hibernate.c3p0.max_size">100</property>
<property name="hibernate.c3p0.timeout">300</property>
<property name="hibernate.c3p0.max_statements">50</property>
<property name="hibernate.c3p0.idle_test_period">3000</property>
</code>

for actual issue thread please check the following link:
http://forums.activiti.org/content/database-server-crash

Re: Activit DB Connection pool leak on WL

jorell — Tue, 12 Aug 2014 03:56:54 GMT

Was anyone able to resolve this issue? We are using c3p0 and occasionally (once a weak) end up with 'hung' threads on awaitAvailable. No error or exceptions in the logs basically all threads are waiting on a db query.

Re: Activit DB Connection pool leak on WL

pksahoo — Tue, 07 Apr 2015 14:58:47 GMT

hi,

How can I configure receive task and signal in Activiti?
use a receive-task and trigger the long-running work in another system/app. once that app completes the operation, "signal" activiti, providing the result of the operation. Than, activiti can continue the process

Re: Activit DB Connection pool leak on WL

jbarrez — Tue, 14 Apr 2015 11:48:54 GMT

This has absolutely nothing to do with the original post here …