-
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
Dev mode fails to reload classes when using reactive rest client #17359
Comments
What versions have you tried? |
Only 1.13.4.Final so far. |
I just tried Quarkus from I'll take a look soon |
Thanks @geoand! |
Fix case of lost TCCL in dev-mode when RESTEasy Reactive reads the HTTP body
…TP body Fixes: quarkusio#17359 (cherry picked from commit 6977868)
Hi @geoand , it looks like the same issue happens with Quarkus 2.0.0.CR2 when you use coroutines. Can you have a look? I updated my reproducer project: 2021-05-19-restclient-dev-mode (2).zip Many thanks! |
Can you open a new issue please? |
Sure |
Describe the bug
We are using resteasy reactive and the reactive rest client in Quarkus 1.13.4.Final, gradle and Kotlin. Everytime the quarkus dev mode reloads the code, Quarkus is broken and we have to restart it.
We were able to break it down to a small reproducer. The problem seems to appear, when we have a POST resource that receives a DTO in the body and passes this dto to a rest client call that receives a generified response (best take a look at the
ReactiveResource:getClient()
method in the reproducer). When the service is freshly startedgradlew quarkusDev
, it all works fine. However, as soon as you change something and quarkus recompiles the code on the next call, it is broken.We added a logging of the received object and there we get the following error:
When we do not add the logging, the response from the resource is just empty.
Please note: In the reproducer, we use the rest client to call the same quarkus service again. This is just to make the reproducer self contained. We also experienced this when calling another service.
Expected behavior
Quarkus Dev Mo
Actual behavior
The classes do not seem to be reloaded correctly.
To Reproduce
./gradlew quarkusDev
The text was updated successfully, but these errors were encountered: