We have a Spring 3 web application on Tomcat 6 that uses several scheduled services via @Scheduled (mainly for jobs that run every night). Now it appears that s
In my case stack trace was absolutely clean, thread started only a couple of time and that's all. The problem was in conflict with another schedule.
Updated
Schedule not work correctly, because I use fixedDelayString and the previous job not ended when was time to start new. After changed schedule to fixedRateString, threads started correctly.