-
Notifications
You must be signed in to change notification settings - Fork 26.4k
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
doRefer in RestProtocol may cause OOM #4458
Comments
@chickenlj hello,we have met the same issues.Is this a bug of dubbo,and how to fixed it? |
I believe this issue has been addressed by #4614. @kaojunsong @HzjNeverStop would you mind to verify? |
@HzjNeverStop should you check this issue now ? |
it's ok, please close this issue, thanks |
Environment
Steps to reproduce this issue
Pls. provide [GitHub address] to reproduce this issue.
Actual Result
What actually happens?
the size of LinkedList [clients] will keep growing, the ResteasyClient hold by it will not release, which will cause OOM easily.
the clients in the linkedList will not release when invoker destroyed, they will only be released when the rest protocol destroyed.
I think the protocol layer should not hold the object's such like client, it should be hold by the invoker and has the same lifecycle with invoker
The text was updated successfully, but these errors were encountered: