quartz定时任务失效问题 #1037
Merged
quartz定时任务失效问题 #1037
+7
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
项目依赖自动使用了Quartz 2.5.1，满足以下条件
Quartz 2.5.1
数据库 PostgreSQL
这正好踩中了 Quartz 官方刚刚认领的一个 bug：
在 2.5.1 里，引入了新的 Util.areNull/containsColumnNames，对 ResultSet 里的列名用大小写敏感比较，
而 PostgreSQL 把列名全变成小写，结果就导致：
明明库里有 trigger 记录，代码却觉得「没有」，抛 NoRecordFoundException导致无法调度，进而定时任务失效
通过把Quartz 版本更新到2.5.2解决定时任务失效问题