-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
JPA writes don't work when using ONLY named data sources since 3.13.0 #42314
Comments
Downgrading back to 3.12.3, it starts working again as expected (updates going through without having such an exception). |
Thanks for reporting. I assume you mean |
/cc @DavideD (hibernate-reactive), @gavinking (hibernate-reactive), @gsmet (hibernate-orm), @mswatosh (db2), @yrodiere (hibernate-orm) |
Yeap, its 3.13 (and 3.12 is working). |
@krisztiankocsis can you provide the full stacktrace? |
Also it would help if you could assemble a small reproducer so that we could reproduce the issue easily. |
/cc @marko-bekhta FYI |
Here is the stack trace. DB updates comming from a Vert.X worker thread seem to work. |
Maybe the issue is with the non-managed thread, and not the multiple data sources. |
We have 3 special threads, so we need a solution to be able to keep them. |
I didn't see any obvious change in 3.13 to explain the different behaviour.. Is there any chance you can create a small reproducer @krisztiankocsis, as Guillaume was suggesting? That'll help us track down the reason for this change of behaviour. Thanks! |
I think I found the culprit and this is embarrassing. |
Fixes quarkusio#42314 Introduced by quarkusio#41547
Should be fixed by #42400. |
I checked the changes in the fix commit. That perfectly makes sense. Thanks for the quick fix @gsmet! |
@marko-bekhta added some tests. I will merge once CI is green. I think I will expedite a 3.13.2 once this is merged as it's rather annoying. Thanks for the report! |
Fixes quarkusio#42314 Introduced by quarkusio#41547 (cherry picked from commit cf5f6bb)
I will announce it on Monday morning but I released 3.13.2 today with the fix. |
Its working! Thanks @gsmet ! |
Fixes quarkusio#42314 Introduced by quarkusio#41547
Describe the bug
We upgrade Quarkus from 3.12.0 -> 3.13.0. We are using 3 named data sources / Hibernate ORM configuration - no default data source is configured. This was working till 3.13.0. DB reads still work, but as soon as we do any update agains a named DB, we get the following exception:
The default datasource has not been properly configured. See https://quarkus.io/guides/datasource#jdbc-datasource for information on how to do that.
Expected behavior
Both DB reads/writes work the same way as in the previous version, and not complaining about unconfigured default data source - we don't need such.
Actual behavior
It is throwing an exception about the missing default data source configuration.
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
21
Quarkus version or git rev
3.13.0
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: