After Quartz is persisted to the database, before or after the task is executed, the task status becomes ERROR.

After the Quartz project went online, the engineering application and the database were on the same server, and often after a task was executed normally, the task status became ERROR, and I found a lot on the Internet.

 

1. Some people say that there is a problem with quartz version 2.1.7, just change the version, but my project is not version 2.1.7, and then I tried 2.2.1-2.3.0, the same error

2. It's strange that my project will report this error almost every time I run it, but only one person on the Internet has mentioned similar problems

 

Suddenly, I looked at the server time, which was more than 2 minutes faster than Beijing time. I adjusted the server time to Beijing time, and ran again. The problem is solved!

 

speculate

Because the application server and database server are the same, even if it is two minutes longer than Beijing time, it should be a benchmark, but changing the time will indeed solve the problem. Do you doubt that QUARTZ will compare the Internet time when operating? ? ? If anyone knows why, please tell me.

Organize your thoughts and make a record of this problem.

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=324711206&siteId=291194637