-
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
Narayana transaction recovery stops work in DEV mode after hot reload #35839
Comments
@michalvavrik I don't recall ever investigating it. You raised the issue so could you not retest it? If not then the transaction team are quite busy: @marcosgopen or @jmfinelli are either of you able to provide Michal with any input on this issue. |
copy that, thanks; I'll re-run the test later this week |
Sure, I will have a look at it. |
Hi @michalvavrik , I tested your reproducer but I got an error: |
sorry @marcosgopen , I had very busy week, sure, there were breaking changes in the meanwhile and I completely forgot about QS PR. Should probably rebase it and resolve conflicts. I'll fix the reproducer next week, thanks so far. |
It would be interesting to see if this is still an issue. |
@michalvavrik could you reproduce the issue with a more recent version of quarkus? |
Hey, I'll answer later this week. |
So, I have tried and I still can reproduce the original issue. Here is how:
Wait till Quarkus ready, then type 's', maybe wait again and try thrice. I am not quite sure how many times I have tried
|
Thanks @michalvavrik for your reproducer, I menaged to reproduce it and I am working to understand what the problem is and solve it. I think that when the destroy method of QuarkusRecoveryService is executed we should also set to null the datasource of QuarkusDataSource. I'll keep you updated. |
Describe the bug
When I change my application in DEV mode and the app is reload, Narayana keeps using the old (previous) Datasource connection even though pool has been closed and new one was created. Details in here #35242 (comment)
Expected behavior
After hot reload, my app still works.
Actual behavior
Warning is logged and periodic recovery doesn't work
How to Reproduce?
Reproducer:
quarkus dev
s
Output of
uname -a
orver
Fedora
Output of
java -version
17
GraalVM version (if different from Java)
23
Quarkus version or git rev
999-SNAPSHOT
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.3
Additional information
No response
The text was updated successfully, but these errors were encountered: