Quartz jobs can run concurrently #146
Assignees
Labels
Comments
sbearcsiro
added a commit
that referenced
this issue
Jun 21, 2021
sbearcsiro
added a commit
that referenced
this issue
Jun 21, 2021
sbearcsiro
added a commit
that referenced
this issue
Jun 21, 2021
Release 1.1.6 - Quartz jobs no longer run concurrently #146 - SettingService.getOrCreateSetting now uses double checked locking #147 - Data Resource names were duplicated in search facets #148 - Image Viewer returns 404 if image id doesn't exist #149 - Add storage location for an image to L2 cache #154
sbearcsiro
added a commit
that referenced
this issue
Jun 21, 2021
Release 1.1.6.1: Note: 1.1.6 was erroneously released missing the change for #149 Changes: - Quartz jobs no longer run concurrently #146 - SettingService.getOrCreateSetting now uses double checked locking #147 - Data Resource names were duplicated in search facets #148 - Image Viewer returns 404 if image id doesn't exist #149 - Add storage location for an image to L2 cache #154
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During periods of high contention for database access, the quartz jobs can take longer to run than their
repeatInterval. This only adds additional contention to an already busy systetm. All existing Quartz jobs should usestatic concurrent = falseas none of them are start time sensitive.The text was updated successfully, but these errors were encountered: