The web application [ROOT] appears to have started a thread named [Timer-2] but has failed to stop it. This is very likely to create a memory leak.Stack trace of thread:
The web application [ROOT] appears to have started a thread named [QuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
2022-12-20 19:00:57,619 WARN (DirectJDKLog.java:180)- The web application [ROOT] appears to have started a thread named [QuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
2022-12-20 19:00:57,620 WARN (DirectJDKLog.java:180)- The web application [ROOT] appears to have started a thread named [QuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
The web application [ROOT] appears to have started a thread named [QuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
2022-12-20 19:00:57,619 WARN (DirectJDKLog.java:180)- The web application [ROOT] appears to have started a thread named [QuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
2022-12-20 19:00:57,620 WARN (DirectJDKLog.java:180)- The web application [ROOT] appears to have started a thread named [QuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.