-
Notifications
You must be signed in to change notification settings - Fork 929
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
Timeout trying to lock table: remove h2 pessimistic locks #441
Comments
ghost
assigned gschueler
Jul 2, 2013
this seems to still occurs : im using the rundeck-2.6.2 on Tomcat 7, just when the notification using a notification example plugin is triggered this happens:
the notification as such works fine |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue #312 cropped up again when using H2 with larger size database and possibly slower disk-speed.
Updating LOCK_TIMEOUT didn't help.
The side-effect was that a Job would appear to never finish, because the lock failure would happen when updating the execution status after a job was done.
to fix: remove use of pessimistic locking, rely on optimistic locks with retries
additional: remove use of pessimistic locks in other places: job abort, job delete, takeover cluster schedule.
The text was updated successfully, but these errors were encountered: