@Disallowcurrentexecution prevents quartz scheduled tasks from executing in parallel

@DisallowConcurrentExecution Forbid concurrent execution of multiple of the same definition JobDetail, This note is added to Job On the class , But it doesn't mean you can't execute more than one at the same time Job, But you can't execute the same JobDefinition( from JobDetail Definition ), But you can do many different things at the same time JobDetail, Illustrate with examples : We have a Job class , be called SyncDataJobTask, And here Job Add this note , Then use this Job Turn on 2 Scheduled tasks , Mission 1: Sync data surface (5 Seconds at a time ), Mission 2: Sync area surface (5 Seconds at a time ), If the mission 2 stay 5 Processing is not completed within seconds , Then the task 2 No new thread will be started to run a new timer , It will not affect the task 1 Normal operation of .
 

@PersistJobDataAfterExecution Indicates when the normal execution is completed Job after ,JobDataMap The data in should be changed , To be called the next time . When using @PersistJobDataAfterExecution When the annotation , To avoid concurrency , Storing data causes confusion , You need to add @DisallowConcurrentExecution

@DisallowConcurrentExecution Used to implement Job On top of the class , Concurrent execution is not allowed , According to my previous understanding, the scheduling framework is not allowed to call at the same time Job class , Later, it was tested and found that this was not the case , It is Job( Mission ) Execution time of [ Such as the need to 10 second ] Time interval greater than task [Interval（5 second )], So by default , The scheduling framework is designed to allow tasks to execute at predetermined intervals , The new thread will be enabled to execute the task immediately . Otherwise, the task will be executed again after the task is completed ！（ This will result in tasks not being executed at pre-defined intervals ）