"Invalid frame type 21" error on RabbitMQ SSL connection after minor upgrade 2.4.6-p9 -> 2.4.6.-p10

[kovalchukVM]

Preconditions and environment

• Magento version 2.4.6-p10
• RabbitMQ 3.13.0
• php-amqplib/php-amqplib ^3.2.0

Steps to reproduce

Steps to reproduce:

1. Use Magento 2.4.6-p10
2. Configure SSL connection in app/env.php

3. Run any queue consumer, e.g. "bin/magento queue:consumers:start async.operations.all"

Expected result

The queue consumer starts and processes messages with no errors.

Actual result

An error message is shown

{"message":"Invalid frame type 21","context":{},"level":"error","level_name":"ERROR","channel":"report","datetime":"2025-05-14T07:10:35.640869+00:00","extra":{},"@timestamp":"2025-05-14T07:10:35.640869Z","severity":"ERROR","original_level":400,"full_message":"Invalid frame type 21\n#0 /app/vendor/php-amqplib/php-amqplib/PhpAmqpLib/Connection/AbstractConnection.php(651): PhpAmqpLib\\Connection\\AbstractConnection->wait_frame(3.0)\n#1 /app/vendor/php-amqplib/php-amqplib/PhpAmqpLib/Channel/AbstractChannel.php(235): PhpAmqpLib\\Connection\\AbstractConnection->wait_channel(0, 3.0)\n#2 /app/vendor/php-amqplib/php-amqplib/PhpAmqpLib/Channel/AbstractChannel.php(352): PhpAmqpLib\\Channel\\AbstractChannel->next_frame(3.0)\n#3 /app/vendor/php-amqplib/php-amqplib/PhpAmqpLib/Connection/AbstractConnection.php(264): PhpAmqpLib\\Channel\\AbstractChannel->wait(Array, false, 3.0)\n#4 /app/vendor/php-amqplib/php-amqplib/PhpAmqpLib/Connection/AMQPLazySSLConnection.php(12): PhpAmqpLib\\Connection\\AbstractConnection->connect()\n#5 /app/vendor/magento/framework-amqp/Config.php(171): PhpAmqpLib\\Connection\\AMQPLazySSLConnection->channel()\n#6 /app/vendor/magento/framework-amqp/Queue.php(156): Magento\\Framework\\Amqp\\Config->getChannel()\n#7 /app/vendor/magento/module-asynchronous-operations/Model/MassConsumer.php(76): Magento\\Framework\\Amqp\\Queue->subscribe(Object(Closure))\n#8 /app/vendor/magento/module-message-queue/Console/StartConsumerCommand.php(94): Magento\\AsynchronousOperations\\Model\\MassConsumer->process(NULL)\n#9 /app/vendor/symfony/console/Command/Command.php(298): Magento\\MessageQueue\\Console\\StartConsumerCommand->execute(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))\n#10 /app/vendor/magento/framework/Interception/Interceptor.php(58): Symfony\\Component\\Console\\Command\\Command->run(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))\n#11 /app/vendor/magento/framework/Interception/Interceptor.php(138): Magento\\MessageQueue\\Console\\StartConsumerCommand\\Interceptor->___callParent('run', Array)\n#12 /app/vendor/magento/framework/Interception/Interceptor.php(153): Magento\\MessageQueue\\Console\\StartConsumerCommand\\Interceptor->Magento\\Framework\\Interception\\{closure}(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))\n#13 /app/generated/code/Magento/MessageQueue/Console/StartConsumerCommand/Interceptor.php(77): Magento\\MessageQueue\\Console\\StartConsumerCommand\\Interceptor->___callPlugins('run', Array, Array)\n#14 /app/generated/code/Magento/MessageQueue/Console/StartConsumerCommand/Proxy.php(143): Magento\\MessageQueue\\Console\\StartConsumerCommand\\Interceptor->run(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))\n#15 /app/vendor/symfony/console/Application.php(1040): Magento\\MessageQueue\\Console\\StartConsumerCommand\\Proxy->run(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))\n#16 /app/vendor/symfony/console/Application.php(301): Symfony\\Component\\Console\\Application->doRunCommand(Object(Magento\\MessageQueue\\Console\\StartConsumerCommand\\Proxy), Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))\n#17 /app/vendor/magento/framework/Console/Cli.php(116): Symfony\\Component\\Console\\Application->doRun(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))\n#18 /app/vendor/symfony/console/Application.php(171): Magento\\Framework\\Console\\Cli->doRun(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))\n#19 /app/bin/magento(23): Symfony\\Component\\Console\\Application->run()\n#20 {main}","type":"application","correlation_id":"7f20c872-ce5f-4f43-b0d6-e63af843400a","user_correlation_id":"7f20c872-ce5f-4f43-b0d6-e63af843400a"}

Additional information

Everything still works as expected on Magento 2.4.6-p9.
The break change was made in 2.4.6-p10 in lib/internal/Magento/Framework/Amqp/Connection/Factory.php class, instead of AMQPSSLConnection::class for SSL connections, now AMQPConnectionFactory::class is used, which takes AMQPConnectionConfig::class as an input parameter.
AMQPConnectionConfig::class uses tcp as a default network protocol; there is no way to change it to ssl.

2.4.6-p9...2.4.6-p10

A possible solution could be a patch that extends Factory class https://github.com/magento/magento2/blob/2.4.6-p10/lib/internal/Magento/Framework/Amqp/Connection/Factory.php by setting the SSL network protocol when SSL is enabled

Release note

Correct network protocol for RabbitMQ SSL connections.

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 @kovalchukVM. 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.

[engcom-Bravo]

Hi @kovalchukVM,

Thanks for your reporting and collaboration.

Adobe Commerce Engineering team started working on this issue. We will reach out to you if we need more information and you will get notified once the issue is fixed. Please leave comments for any further questions.

Till then we are moving this issue to On Hold.

Thank you!

[chrisgan]

We patched successfully based on the suggestion by @kovalchukVM thanks

This has been tested on 2.4.6-p10 and confirmed to resolve the issue with SSL connections.

diff --git a/vendor/magento/framework-amqp/Connection/Factory.php b/vendor/magento/framework-amqp/Connection/Factory.php
--- a/Connection/Factory.php
+++ b/Connection/Factory.php
@@ -39,6 +39,7 @@
         // Set SSL options if SSL is enabled
         if ($options->isSslEnabled()) {
             $config->setIsSecure(true);
+            $config->setNetworkProtocol(\Magento\Framework\Amqp\Config::SSL);
             $sslOptions = $options->getSslOptions();
             if ($sslOptions) {
                 if (isset($sslOptions['cafile'])) {
``` 

[engcom-Bravo]

Hi @kovalchukVM,

We got reply from Internal team as follows

During our review and comparison of Magento versions 2.4.6-p10 and 2.4.8, we identified a critical behavioral change related to SSL connections and AMQP protocol configuration.

Issue Summary:
In Magento 2.4.6-p10, the php-amqplib/php-amqplib package is used at version v3.5.3. In this version:
The isSecure() method does not set the network protocol explicitly.
As a result, even when SSL is enabled, the default protocol remains TCP, which may lead to unexpected issues in secure environments.
However, in Magento 2.4.8, the same package has been updated to v3.7.3, which introduces the setIsSecure(bool $isSecure) method. This method:
Explicitly sets the protocol to TLS when SSL is enabled.
Changes the default behavior and can cause discrepancies if not handled correctly in custom or legacy implementations.
Root Cause:
The update to php-amqplib/php-amqplib v3.7.3 in Magento 2.4.8 introduces an automatic switch to the TLS protocol when SSL is enabled, which differs from the behavior in v3.5.3 where TCP was used regardless.
Quick Fix:
To maintain compatibility in Magento 2.4.6-p10 or align behavior manually in custom code, apply the following patch:
Add the following line after this line in Factory.php (L41):
$config->setNetworkProtocol(\Magento\Framework\Amqp\Config::SSL);
Alternative Solution:
Upgrade the
php-amqplib/php-amqplib package to v3.7.3 or higher, ensuring full compatibility and enabling secure connections over TLS by default.
Note: We are currently discussing with the PO to determine whether a hotfix is necessary. The issue has been identified in Git-based installations where the php-amqplib/php-amqplib package is locked to v3.5.3. This version introduces a change in behavior regarding the network protocol for secure connections, which differs from the composer-based installations (e.g., Magento 2.4.6-p10) that use v3.2.0. As a result, the problem is specific to environments using Git-based setups with the updated library version.

Thanks.