-
Bug Report
-
Resolution: Cannot Reproduce
-
L3 - Default
-
None
-
spring-boot 3.2.1
-
None
When trying to bootstrap a new DB using Camunda BPM Spring Boot Starter the following exception occurs:
Caused by: org.postgresql.util.PSQLException: Cannot commit when autoCommit is enabled. at org.postgresql.jdbc.PgConnection.commit(PgConnection.java:772) ~[postgresql-42.2.5.jar:42.2.5] at com.zaxxer.hikari.pool.ProxyConnection.commit(ProxyConnection.java:361) ~[HikariCP-3.2.0.jar:na] at com.zaxxer.hikari.pool.HikariProxyConnection.commit(HikariProxyConnection.java) ~[HikariCP-3.2.0.jar:na] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na] at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na] at org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy$TransactionAwareInvocationHandler.invoke(TransactionAwareDataSourceProxy.java:236) ~[spring-jdbc-5.1.5.RELEASE.jar:5.1.5.RELEASE] at com.sun.proxy.$Proxy100.commit(Unknown Source) ~[na:na] at org.camunda.bpm.spring.boot.starter.configuration.impl.custom.EnterLicenseKeyConfiguration.postProcessEngineBuild(EnterLicenseKeyConfiguration.java:76) ~[camunda-bpm-spring-boot-starter-3.2.1.jar:3.2.1] ... 154 common frames omitted
However, when reverting back to 3.2.0, this error is not present.
Also, when using version 3.21, after that exception if i restart the application, camunda seems to be running fine.
Using the following configuration:
Spring-Boot: (v2.1.3.RELEASE) Camunda BPM: (v7.10.3-ee) Camunda BPM Spring Boot Starter: (v3.2.1) openjdk version "11.0.1" 2018-10-16 OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.1+13) OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.1+13, mixed mode)
Note that apparently in older version of the postgresql driver (i'm using 42.2.5) this is not autocommit thing is not checked; hence maybe you not finding this in some automated tests. (see https://www.postgresql.org/message-id/1379496313.51692.YahooMailNeo%40web162904.mail.bf1.yahoo.com)
This is the controller panel for Smart Panels app
[CAM-9928] Camunda BPM Spring Boot Starter fails to bootstrap db
We lost access to the support project and we are investigating with Camunda to restore access to it 
Hi Oliver,
thanks for your patience.
I assume that the HikariCP you are using enables the auto-commit feature by default. Can you reproduce the problem also with a vanilla Camunda Spring Boot Starter project without using HikariCP? Did you already tried to disable auto-commit via the JDBC url parameter?
Cheers,
Tassilo
Hi Olivier,
I close this issue since we received no response from you. If you need further assistance, you could also consider to create a thread on our Community Forum [1].
Cheers,
Tassilo
Sorry didnt' get any notifications of your responses, we don't use or enable HikariCP (but it might get enabled through a dependency).
I'll try to disable autocommit via the url parameters
Hi Oliver,
I will investigate if the observed behavior you are facing is actually a bug and come back to you as soon as possible.
From you provided configuration I can see that you are using the enterprise edition. Why did you raise this issue in the community and not in the support project? The difference is that support cases are subjected to the SLAs.
Cheers,
Tassilo