quarkus: Reactive DB connection causes problems

Hi guys! First, I want tell you all, thank you for such a great job, what do you do with Quarkus!

Describe the bug I have 2 connections to the same DB in my applications.properties file. It’s looks like this:

quarkus.datasource.jdbc=true
quarkus.datasource.db-kind=mysql
%dev.quarkus.datasource.jdbc.url=jdbc:mysql://0.0.0.0:6603/mydatabase
quarkus.datasource.driver=com.mysql.cj.jdbc.Driver
quarkus.datasource.username=username
quarkus.datasource.password=password

#and reactive connection
quarkus.datasource.reactive=true
%dev.quarkus.datasource.reactive.url=vertx-reactive:mysql://0.0.0.0:6603/mydatabase

in same file i have some property for my public key:

mp.jwt.verify.publickey.location=${share.path}/resources/publicKey.pem

${share.path} - i get from my DB, with my custom DatabaseSource.

Expected behavior it’s work fine, till i add reactive DB connection to my application.properties

Actual behavior if i add reactive DB connection, then I get an error message, that variable ${share.path} is no longer recognized from Quarkus. It’s like Quarkus don’t know anymore, wich connection it should to use to get ${share.path} properties from DB.

To Reproduce here is some simple reproducer with code from my project.

It will be nice to know, why is this so 😃

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 33 (18 by maintainers)

Most upvoted comments

Hi @MadinaS,

The issue you were facing is the same reported here: https://github.com/quarkusio/quarkus/issues/10570. Updating to Quarkus 1.6.1 should fix your issue.

I’ve tested it in your second repro project and it does work. For now, I’m closing the issue. Please, let me know if you need anything else.

Ok, let me have a look.

I just want to cover all possible bases