A Java expression is taking long to complete and the below error is thrown.  We like to understand the best way to configure camunda to deal with these long running tasks.

 

Entered a ticket based upon conversation with our success manager (Ryan Warner)

 

1. 1. 1. Error querying database.  Cause: java.sql.SQLException: Connection has already been closed.

1. 1. 1. The error may exist in org/camunda/bpm/engine/impl/mapping/entity/Execution.xml

1. 1. 1. The error may involve org.camunda.bpm.engine.impl.persistence.entity.ExecutionEntity.selectExecutionsByProcessInstanceId

1. 1. 1. The error occurred while executing a query

1. 1. 1. SQL: select * from ACT_RU_EXECUTION     where PROC_INST_ID_ = ?

1. 1. 1. Cause: java.sql.SQLException: Connection has already been closed.

                              at org.apache.ibatis.exceptions.ExceptionFactory.wrapException(ExceptionFactory.java:30)

                              at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:149)