Closed LuboTerifaj closed 4 months ago
@wmedvede @fjtirado fyi
@LuboTerifaj Adding quarkus.devservices.enabled=false to application.properties should do the trick. That property needed only if running in dev mode. Using quarkus in not dev mode should work as it is currently is When dev mode and devservices is enabled, an embedded data-index is run, that embedded data index uses embedded postgres. To disable that (and any other db quarkus might be tempted to run and that will very likely interfere with your db) you need to disable devservices.
Describe the bug
When persistence is enabled in Quarkus project, according to logs, the embedded PostgreSQL database is used regardless of application.properties setting.
Added pom dependencies:
application.properties file content:
See the part of the log:
Complete log:
Originally reported by @qb0C80aE
Expected behavior
Configured PostgreSQL database is used.
Actual behavior
Embedded PostgreSQL database is used.
How to Reproduce?
For more information see the instructions in https://kiegroup.github.io/kogito-docs/serverlessworkflow/main/persistence/persistence-with-postgresql.html
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
The issue is reproducible in various environments. For example:
Env1:
podman 4.2.0
RHEL 8.7
java 11
Maven 3.8.6
Env2:
docker 25.0.3
Fedora 39
OpenJDK 11
Maven 3.8.8