Quartz - fix job refire behavior, improve dep. bean job scenario #42223
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.
Follows up on #42072 and superseeds #42096
Related to #42034
First commit fixes a case that we discussed with @mkouba over on Zulip which is that job re-fires (via
JobExecutionException
) should not spawn new bean instance but instead reuse existing one.The other commit is a fix that makes sure we use the same bean instance for both,
execute()
andinterrupt()
methods.@ilia1243 FYI, this is a follow up on the discussion from last week; hopefully this no longer has the same shortcomings :)