Web Application Memory Leak: HikariPool-3 housekeeper Thread Not Stopped

During the startup of a web application, a thread named 'HikariPool-3 housekeeper' is created. However, this thread might not be properly stopped when the application shuts down, leading to a potential memory leak. This issue can arise if the application fails to terminate the thread gracefully, resulting in a situation where the thread continues to consume resources even after the application has closed. The specific thread stack trace provides valuable information about the methods, classes, files, and line numbers involved, aiding developers in analyzing and resolving the issue.