Unreleased Timer Threads in File Connector Leading to High CPU Usage

[sajith-madhusanka]

Description

The Timer threads created via the file lock mechanism of the file connector are not canceled upon undeploying the Carbon application. Instead, a new Timer thread is created each time the same Carbon application with the file connector configuration is deployed. Since a file lock timer thread is created per file connector configuration, this behavior leads to the accumulation of abandoned Timer threads, causing the thread count to increase and ultimately resulting in high CPU usage.

Steps to Reproduce

• Deploy a Carbon application that uses file operations.
• Invoke the service/API to trigger the file operation (need to trigger the file operation to create the file lock object).
• Capture a thread dump and check for timer threads.
• Redeploy the same Carbon application and invoke the service/API again.
• Capture another thread dump and observe that a new timer thread is created without removing the older one.
• Repeat the process multiple times and confirm that new timer threads continue to be created.

Version

4.1.0

Environment Details (with versions)

No response