Cron - If a misbehaving cron_job starts a transaction it can error and leave the transaction open impacting further jobs run after the misbehaving job

[steven-hoffman-jomashop]

Preconditions and environment

• 2.4.7

Steps to reproduce

A Magento module with a cron job in the default group, with a scheduled time that overlaps with other crons.
The new cron job runs before some other cron jobs.
The new cron job starts a transaction and then throws an error leaving the transaction open.

Expected result

Later cron jobs all start with transaction level=0. (And the DB does not have an open transaction).

Actual result

Later cron jobs all start with transaction level=1. (And the DB has an open transaction).

Also, increased rates of lock wait timeout as the locks taken are kept open until all the cron jobs finish running.

Additional information

Note: It is not currently possible to access all connections from ResourceConnection as the named connections from the connections property are not exposed via a public method.
Note: Closing all connections is possible via closeConnection(null). (Though this may unlock locks held by the ProcessCronQueueObserver)

It would be a significant improvement if ProcessCronQueueObserver checked if the default connection's Transaction level was not equal to 0, and if so, it rolled back until it reached zero. (Or closing the connection; or even aborting would be better than starting a new job with transaction level not equal to zero).

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @steven-hoffman-jomashop. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.