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
If the CP is down, and the gateway is constantly trying to connect to the CP, the thread count can be increased. Even in the logs, there were multiple connectivity errors. But, once the CP is up and running again these unwanted threads in the waiting state should be cleared from the memory. However, we could see those threads never get cleared from the memory until the gateway node restarted again. it continues to stay in the memory for days.
Steps to Reproduce
Create a setup. (One CP and One Gateway)
Profile both CP and GW.
Start both CP and GW.
Wait for 5 minutes till the servers settle down.
Collect the thread count and thread dump.
Stop the CP node.
Wait 15 minutes and collect the thread count and thread dump.
Start the CP node after 15 minutes.
Wait for 15 minutes and collect thread count and thread dump.
Affected Component
APIM
Version
4.1.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
APIM
The text was updated successfully, but these errors were encountered:
Description
If the CP is down, and the gateway is constantly trying to connect to the CP, the thread count can be increased. Even in the logs, there were multiple connectivity errors. But, once the CP is up and running again these unwanted threads in the waiting state should be cleared from the memory. However, we could see those threads never get cleared from the memory until the gateway node restarted again. it continues to stay in the memory for days.
Steps to Reproduce
Affected Component
APIM
Version
4.1.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
APIM
The text was updated successfully, but these errors were encountered: