Hi Team,
Issue: DB Connections are not released back to the pool immediately once we stop the workflows. They are only released back to the pool after the removeAbandonedTimeout is met which is 10 minutes in my case.
Problem Faced: If i have multiple parallel workflows with http-connector async jobs, running each of async job takes up a connection, if for some reason i have to stop the workflows due to some exceptions or so… Then the connection is not released though all the workflows are stopped. …
If i have started 20 workflows and stopped them, i will not have connections available for new workflows to start. i have to wait for 10 minutes to start new flows.
We have the following configuration in the server.xml for the data base
<Resource name=“jdbc/ProcessEngine”
auth=“Container”
type=“javax.sql.DataSource”
factory=“org.apache.tomcat.jdbc.pool.DataSourceFactory”
uniqueResourceName=“process-engine”
driverClassName=“org.h2.Driver”
url=“jdbc:h2:./camunda-h2-dbs/process-engine;MVCC=TRUE;TRACE_LEVEL_FILE=0;DB_CLOSE_ON_EXIT=FALSE”
defaultTransactionIsolation=“READ_COMMITTED”
username=“xxxxxx”
password=“xxxx”
maxActive=“20”
minIdle=“5”
maxIdle=“20”
testOnBorrow=“true”
logAbandoned=“true”
removeAbandoned=“true”
removeAbandonedTimeout=“600”
validationInterval=“30000”
validationQuery=“SELECT 1” />
Did any one fo you face this problem ?
Also if i am using the external-tasks to perform the same operations the data base connection are not held for that long they are getting released immediately.
Thanks,
Sai Arun J