https Rabbit MQ heartbeat issues

[frostblogNet]

Preconditions and environment

• Magento| Adobe Commerce 2.4.5 | 2.4.6
• If you connect Magento a AWS RabbitMQ over https connection will be closed after about 10 minutes due to an heartbeat issue with is probably fixed in 3.5.3 see https://github.com/php-amqplib/php-amqplib/milestone/31?closed=1
• The problem only occure when https is used which is the default for aws rabbit mq.

Steps to reproduce

Setup Magento 2.4.5 or 2.4.6 and connect it to a AWS Rabbit MQ using https. Set Stock Update to Async in the Backend. Start the consumer and send Stock update Messages to the Rest-Api.

After about 10 minutes the consumer will stock processing this messages. Only after a restart of the consumer he will continue processing.

Expected result

The consumer will send proper heartbeat to the rabbit mq and will continue processing messages until we will be stopped.

Actual result

consumer is running with a broken connection and will not process messages

Additional information

No response

Release note

php-amqplib/php-amqplib needed update due to heartbeat issue over https

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 @frostblogNet. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• 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-Hotel. 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

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[engcom-Hotel]

Hello @frostblogNet,

Thanks for the report and collaboration!

We are trying to reproduce the issue in 2.4-develop, meanwhile, we have a query, can you please let us know if you are using any third-party extension for the below step:

Set Stock Update to Async in the Backend. Start the consumer and send Stock update Messages to the Rest-Api.

Can you please elaborate on the above point a little bit more?

Thanks

[engcom-Hotel]

Dear @frostblogNet,

We have noticed that this issue has not been updated for a long period. Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

Regards