Consult the Spring community.

Spring defaults the Quartz property org.quartz.jobStore.dontSetAutoCommitFalse to true, which means Quartz will not turn off auto-commit mode on the database connections that it uses. This is the opposite of Quartz's own default for this setting. If your connection is defaulting to have auto-commit on, then you'll run into all sorts of strange problems relating to data inconsistencies. The most common symptom is triggers that are stuck in the "ACQUIRED" state. To fix this problem, set the org.quartz.jobStore.dontSetAutoCommitFalse property to false.