-
Notifications
You must be signed in to change notification settings - Fork 690
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database Init fails after upgrade to Spring Boot 2.4.x #1231
Comments
What versions of Exposed, MariaDB driver, Spring Boot do you use? |
Also, looks similar to https://mariadb.com/kb/en/pooledconnection-with-wrong-user-credentials-timeouts-without-information/ and look at that test in the MariaDB driver. |
Exposed: version 0.31.1 |
So the only change is an upgrade of the Spring Boot version? |
Correct, that is the only change. I might look into that wrong user credentials bug you mentioned, it might be that after upgrading to spring boot 2.4.x the credentials are loaded from the wrong profile (because spring boot changed the profiles loading from the application.yml a bit). |
@benjaminkomen , were you able to find out the problem? |
I haven't looked at it again, just kept spring boot on version 2.3.5. Maybe good to look into again next week, thx for the reminder. |
Exposed 0.32.1 depends on Spring Boot 2.3.5, so please check the that version |
Interesting, with Exposed 0.32.1 and with spring boot 2.5.1 it does seem to work! But what has changed, I wonder.. |
Thanks for your help @Tapac , I'm going to close this issue, as it has been resolved for me. |
After upgrading from Spring boot 2.3.5.RELEASE to 2.4.x our application cannot initialise the database connection using Exposed anymore. The full stack trace is attached below.
The piece of code where the exceptions happens:
The datasource injected in this function is just a datasource with username, password and URL of type MariaDbPoolDataSource where the URL is:
jdbc:mariadb:aurora://***REDACTED***-***REDACTED***.cluster-***REDACTED***.eu-west-1.rds.amazonaws.com:3306/***REDACTED***?connectTimeout=60000&minPoolSize=0&maxIdleTime=60
Any ideas what is going on?
Full stack trace:
The text was updated successfully, but these errors were encountered: