Skip to content

Max CPU utilisation and application becomes irresponsive when we upgraded to 3.35.0 #584

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

Closed
gmhoolageri opened this issue Mar 27, 2024 · 2 comments
Labels
SDK Issue pertains to the SDK itself and not specific to any service

Comments

@gmhoolageri
Copy link

Our application was running fine until we upgraded to 3.35.0 of OCI SDK. The application started hitting high CPU utilisation in 5 days and application became irresponsive. Upon inspecting the thread dump we came to know that there are 9000+ threads are there active in our application which is too high. We looked at thread types and found at least 8000+ threads were of type idle-connection-monitor-thread. We immediately looked into SDK documentation and came to know that 3.31.x has the idle connection monitoring feature enabled by default and we can turn it off.

It is always a good design to release a feature which is turned off by default than turned off. My recommendation is to turn off the feature by default in upcoming java sdk releases.

@rkumarpa rkumarpa added the SDK Issue pertains to the SDK itself and not specific to any service label Apr 4, 2024
@rkumarpa
Copy link
Contributor

rkumarpa commented Apr 4, 2024

The issue has been resolved in 3.39.0 . Please see this ticket for more info - #587

@rkumarpa
Copy link
Contributor

We are closing this ticket. Please reopen it if you still see the issue with the versions 3.39.0 or later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SDK Issue pertains to the SDK itself and not specific to any service
Projects
None yet
Development

No branches or pull requests

2 participants