-
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
Avoid calling ResteasyProviderFactory.getInstance() when popping #41431
Conversation
When popping provider factory, what we actually want is pop it if something has been pushed. It is better handled by setting a boolean if something has been pushed. This allows class loading issues when the class loader has been closed and the request is still processing. Related to quarkusio#41233
I can't say I understand this one. I'll look at it tomorrow |
Status for workflow
|
It's related to this issue: #41233 And more specifically to this stacktrace that I got with my code dumping the stack when a CL is accessed while closed:
I tracked where this was called and it was in the Now I'm not entirely sure how the CL gets closed by the time we arrive there but in any case, what we are doing is not ideal given what we really want is to pop when we have pushed. The test was copied but really we just want to have a boolean that indicates we have pushed something and we need to pop it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha, makes sense!
When popping provider factory, what we actually want is pop it if something has been pushed.
It is better handled by setting a boolean if something has been pushed.
This allows class loading issues when the class loader has been closed and the request is still processing.
Related to #41233