I searched the quartz.properties in the classpath, and I did find a quartz.properties, and delete it.
But the issue still exist after restart.
Clear the classpath
I found many backup jars in the root of the deploy dir, I delete the backup jars like this:
At last, there is only one myjob.jar in the classpath, and the jar does not contain any quartz.properties in it. Restart the app, the problem disappeared.
3. Conclusion
To summarize:
- There is no need for the quartz.properties file for most projects, If you find one, just delete it.
- If you need the file, you can specify the content of the thread count properites like this:
If you don’t find any quartz.properties file in the classpath, check your jars, and make sure there are not any backup jars in the classpath