Skip to content

QUARKUS_DATASOURCE_POSTGRESQL_JDBC_URL not working in 0.104.2 #48451

@dgomezleon

Description

@dgomezleon

Describe the bug

I have detected a difference between version 0.104.1 and 0.104.1. This works for me

$ docker run  --env NESSIE_VERSION_STORE_PERSIST_JDBC_DATASOURCE=postgresql --env NESSIE_VERSION_STORE_TYPE=JDBC --env QUARKUS_DATASOURCE_POSTGRESQL_JDBC_URL=jdbc:postgresql://nessie-postgresql:5432/bitnami_nessie  -p 19120:19120 ghcr.io/projectnessie/nessie:0.104.1

However, the same command for 0.104.2 produces the following error:

$ docker run  --env NESSIE_VERSION_STORE_PERSIST_JDBC_DATASOURCE=postgresql --env NESSIE_VERSION_STORE_TYPE=JDBC --env QUARKUS_DATASOURCE_POSTGRESQL_JDBC_URL=jdbc:postgresql://nessie-postgresql:5432/bitnami_nessie  -p 19120:19120 ghcr.io/projectnessie/nessie:0.104.2

...
2025-06-18 09:59:50,528 ERROR [io.qua.run.Application] (main) Failed to start application: java.lang.RuntimeException: Failed to start quarkus
        at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)
        at io.quarkus.runtime.Application.start(Application.java:101)
        at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:119)
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:80)
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:51)
        at io.quarkus.runtime.Quarkus.run(Quarkus.java:144)
        at io.quarkus.runner.GeneratedMain.main(Unknown Source)
        at io.quarkus.bootstrap.runner.QuarkusEntryPoint.doRun(QuarkusEntryPoint.java:68)
        at io.quarkus.bootstrap.runner.QuarkusEntryPoint.main(QuarkusEntryPoint.java:36)
Caused by: io.quarkus.arc.InactiveBeanException: Bean is not active: SYNTHETIC bean [class=io.agroal.api.AgroalDataSource, id=gR3T7P8K5d04qa8N9hC2NJSdjvo]
Reason: Datasource 'postgresql' was deactivated automatically because its URL is not set. To activate the datasource, set configuration property 'quarkus.datasource."postgresql".jdbc.url'. Refer to https://quarkus.io/guides/datasource for guidance.
To avoid this exception while keeping the bean inactive:
        - Configure all extensions consuming this bean as inactive as well, if they allow it, e.g. 'quarkus.someextension.active=false'
        - Make sure that custom code only accesses this bean if it is active
 ...

It works fine with

$ docker run --env NESSIE_VERSION_STORE_TYPE=JDBC --env QUARKUS_DATASOURCE_JDBC_URL=jdbc:postgresql://nessie-postgresql:5432/bitnami_nessie  -p 19120:19120 ghcr.io/projectnessie/nessie:0.104.2  

But with the following warning:

Using legacy datasource configuration under quarkus.datasource.*: please migrate to quarkus.datasource.postgresql.* and set nessie.version.store.persist.jdbc.datasource=postgresql

Expected behavior

Using NESSIE_VERSION_STORE_PERSIST_JDBC_DATASOURCE=postgresql + QUARKUS_DATASOURCE_POSTGRESQL_JDBC_URL should work as in previous versions.

Actual behavior

QUARKUS_DATASOURCE_POSTGRESQL_JDBC_URL does not work, only QUARKUS_DATASOURCE_JDBC_URL.

How to Reproduce?

Execute

$ docker run  --env NESSIE_VERSION_STORE_PERSIST_JDBC_DATASOURCE=postgresql --env NESSIE_VERSION_STORE_TYPE=JDBC --env QUARKUS_DATASOURCE_POSTGRESQL_JDBC_URL=jdbc:postgresql://nessie-postgresql:5432/bitnami_nessie  -p 19120:19120 ghcr.io/projectnessie/nessie:0.104.2

Output of uname -a or ver

Linux 76dd58bbb8e3 6.10.14-linuxkit #1 SMP Fri Nov 29 17:22:03 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

Output of java -version

21.0.7

Quarkus version or git rev

3.23.3

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/configarea/jdbcIssues related to the JDBC extensionskind/bugSomething isn't workingtriage/out-of-dateThis issue/PR is no longer valid or relevant

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions