-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Queue Management Issue (DB MQ) #37559
Comments
Hi @makkoff. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
Hi @engcom-Bravo. Thank you for working on this issue.
|
Hi @makkoff, Thank you for reporting and collaboration. Verified the issue on Magento 2.4.6 cloud instance and the issue is not reproducible.Kindly refer the attached video. Steps to reproduce
We are able to place the order successfully. Untitled.23.mp4Kindly recheck the behaviour on Magento 2.4.6 cloud instance and elaborate steps to reproduce if the issue is still reproducible. Thanks. |
Hi @makkoff, Kindly provide us latest update on this #37559 (comment) you are able to reproduce the issue or still working on this issue and also please let us know if we are missing anything. Thanks. |
Hi @makkoff, We have noticed that this issue has not been updated since long time. Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this. Thanks. |
Preconditions and environment
Steps to reproduce
Note: Can reproduce this issue only at magneto cloud staging environment since there we use slave connection to the DB.
Expected result
The order was placed and the
inventory.reservations.updateSalabilityStatus
queue was successfully addedActual result
Getting the error:
the
inventory.reservations.updateSalabilityStatus
queue fails because the\Magento\MysqlMq\Model\ResourceModel\Queue::saveMessage
returns 0 instead of the last insert id(message id).I added a rewrite for
Magento\ResourceConnections\DB\Adapter\Pdo\MysqlProxy
to log the last insert IDs of slave and master connections:And here is the result:
[2023-05-30T12:47:36.737265+00:00] db_queue_logger.DEBUG: CONNECTIONS LOG: [] [] [2023-05-30T12:47:36.737307+00:00] db_queue_logger.DEBUG: MASTER Connection last insert ID - 9312 [] [] [2023-05-30T12:47:36.737347+00:00] db_queue_logger.DEBUG: MASTER Connection last insert ID with "queue" table - 9312 [] [] [2023-05-30T12:47:36.737387+00:00] db_queue_logger.DEBUG: SLAVE Connection last insert ID - 0 [] [] [2023-05-30T12:47:36.737425+00:00] db_queue_logger.DEBUG: SLAVE Connection last insert ID with "queue" table - 0
Additional information
DB query log:
...
...
Release note
This part of code was changed in 2.4.6
\Magento\ResourceConnections\DB\Adapter\Pdo\MysqlProxy::selectConnection
Triage and priority
The text was updated successfully, but these errors were encountered: