HikariDataSource has been closed

Hi all

in our UAT environment, we’re facing an exception apparently concerning to database pooling:

java.sql.SQLException: HikariDataSource HikariDataSource (flowable-rest) has been closed

This occurs constantly, and is complemented with:

org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is java.sql.SQLException: HikariDataSource HikariDataSource (flowable-rest) has been closed.
at org.springframework.jdbc.datasource.DataSourceTransactionManager.doBegin(DataSourceTransactionManager.java:307) ~[spring-jdbc-5.2.2.RELEASE.jar:5.2.2.RELEASE]
at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:376) ~[spring-tx-5.2.2.RELEASE.jar:5.2.2.RELEASE]
at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:137) ~[spring-tx-5.2.2.RELEASE.jar:5.2.2.RELEASE]
at org.flowable.common.spring.SpringTransactionInterceptor.execute(SpringTransactionInterceptor.java:56) ~[flowable-spring-common-6.5.0.jar:6.5.0]
at org.flowable.common.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:30) ~[flowable-engine-common-6.5.0.jar:6.5.0]
at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:56) ~[flowable-engine-common-6.5.0.jar:6.5.0]
at org.flowable.common.engine.impl.cfg.CommandExecutorImpl.execute(CommandExecutorImpl.java:51) ~[flowable-engine-common-6.5.0.jar:6.5.0]
at org.flowable.common.engine.impl.query.AbstractQuery.list(AbstractQuery.java:117) ~[flowable-engine-common-6.5.0.jar:6.5.0]
at org.flowable.eventregistry.impl.management.DefaultEventRegistryChangeDetectionManager.detectChanges(DefaultEventRegistryChangeDetectionManager.java:50) ~[flowable-event-registry-6.5.0.jar:6.5.0]

Our aim, is to deploy in the REST engine (flowable-rest) some jars with custom Service Tasks, and we succeeded on that…the problem is that, in the background (in the logs), we’re facing this error. Even if we remove the custom jars from /WEB-INF/lib, this error persists…
We are not Hikari experts and/or ther’s something we’re not detecting…can you please help us identifying what might be the cause for this behaviour. For example: we can’t even understand which batch is triggering the exception.

Thanks in advance

Our mistake. Stoped tomcat, cleaned everything and everything wirked ok.

1 Like