You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
rkumarpa
added
the
SDK
Issue pertains to the SDK itself and not specific to any service
label
Apr 4, 2024
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.
The text was updated successfully, but these errors were encountered: