-
-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explore how to remove quartz scheduler #361
Comments
syjer
changed the title
Explore how to remove quartz
Explore how to remove quartz scheduler
Nov 1, 2017
syjer
added a commit
that referenced
this issue
Nov 22, 2018
syjer
added a commit
that referenced
this issue
Nov 22, 2018
…ler, add skip locked in for update clause
syjer
added a commit
that referenced
this issue
Nov 22, 2018
syjer
added a commit
that referenced
this issue
Nov 22, 2018
syjer
added a commit
that referenced
this issue
Nov 22, 2018
syjer
added a commit
that referenced
this issue
Nov 22, 2018
syjer
added a commit
that referenced
this issue
Nov 22, 2018
syjer
added a commit
that referenced
this issue
Nov 22, 2018
syjer
added a commit
that referenced
this issue
Nov 22, 2018
syjer
added a commit
that referenced
this issue
Nov 22, 2018
syjer
added a commit
that referenced
this issue
Nov 23, 2018
…e multi threaded test, the transactional annotation are not applied, and thus may cause issues. As an additional measure, the job class has been moved in a separate package
syjer
added a commit
that referenced
this issue
Nov 23, 2018
syjer
added a commit
that referenced
this issue
Nov 23, 2018
done. |
cbellone
pushed a commit
that referenced
this issue
Nov 23, 2018
* #361 remove pgsql quartz vacuum jobs * #361 move cleanup for demo mode and cleanup unreferenced blob to spring scheduled jobs * #361 move special price token generation job in spring managed scheduler, add skip locked in for update clause * #361 move send offline payment reminder to event organizer to spring scheduled jobs * #361 move send email job to spring scheduled jobs * #361 javadoc * #361 move process pending reservations job in spring managed scheduler * #361 remove quartz cron trigger builder helper * #361 move send offline payment reminder job in spring managed scheduler * #361 move send ticket assignment reminder job in spring managed scheduler * #361 move cleanup expired pending reservation job in spring managed scheduler * #361 remove unused query * #361 remove quartz, switch last job * #361 rename job component, email load ids waiting for processing: add a limit of 100 * #361 make some methods publics and transactional, as discovered in the multi threaded test, the transactional annotation are not applied, and thus may cause issues. As an additional measure, the job class has been moved in a separate package * #361 misc cleanup/transactional:readonly=true * #361 add test for cleanupUnreferencedBlobFiles
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the jobs are handled by quartz, but it's quite hard to handle the addition/update of jobs as they are persisted in the database: quartz is quite picky and may launch errors when the jobs definition are not exactly aligned with what he expect, it's problematic when we rollout on multiple servers.
We have the following jobs that are marked as
@DisallowConcurrentExecution
:Check how we could make them handled directly by spring: the hard job will be to make them able to be run by multiple instances, without problems.
The text was updated successfully, but these errors were encountered: