In MDL-50009, we patched the task system so that any plugin (or potentially core) task which left a database transaction uncommitted couldn't prevent the task system from doing its job.
I would really like to see this ported to supported releases, if possible, for the following reasons:
- It's arguably a bug. The cron log is reporting that tasks have completed successfully when, in fact, everything they have done (in the database) is rolled back afterwards. Also, a single ad-hoc task that leaves a transaction open breaks the entire task system.
- Unlike some other areas where badly-coded plugins can break things (e.g. Javascript or CSS), the effects of this problem can be subtle and hard to detect.
Please see the original issue for more details if required.
- has been marked as being related by
-
MDL-50009 Prevent scheduled tasks from leaving unfinished db transactions
- Closed