admin管理员组

文章数量:1123785

I've installed RabbitMQ on a Subdomain (e.g. rabbitmq.example) and integrated it in Shopware 6.

Now the messages are processed by RabbitMQ, but not the low_priority or failed messages. They still remain in database.

In the Shopware .env.local config the RabbitMQ URLs are defined like this:

MESSENGER_TRANSPORT_DSN=amqp://admin:[email protected]:14021/%2f/messages
MESSENGER_TRANSPORT_LOW_PRIORITY_DSN=amqp://admin:[email protected]:14021/%2f/low_priority
MESSENGER_TRANSPORT_FAILURE_DSN=amqp://admin:[email protected]:14021/%2f/failed

Probably it's just a wrong URL defined. If bin/console messenger:setup-transports is executed within Shopware console the following error message appears:

CRITICAL  [console] Error thrown while running command "messenger:setup-transports". Message: "No transport supports the given Messenger DSN." ["exception" => Symfony\Component\Messenger\Exception\InvalidArgumentException^ { …},"command" => "messenger:setup-transports","message" => "No transport supports the given Messenger DSN."]

In TransportFactory.php line 54:

  No transport supports the given Messenger DSN.


messenger:setup-transports [<transport>]

In the Shopware messenger config file config/packages/messenger.yaml the following lines are defined:

framework:
    messenger:
        transports:
            messages:
                dsn: '%env(MESSENGER_TRANSPORT_DSN)%'
                options:
                    queue_name: messages
            low_prio:
                dsn: '%env(MESSENGER_TRANSPORT_LOW_PRIORITY_DSN)%'
                options:
                    queue_name: low_priority
            failed:
                dsn: '%env(MESSENGER_TRANSPORT_FAILURE_DSN)%'
                options:
                    queue_name: failed

I already tried different URLs like suggested in .html#changing-the-transport with URL parameter ?queue_name=low_priority and ?queue_name=failed but the error remains.

Thanks in advance and best regards

本文标签: shopware6RabbitMQ Shopware integration messenger transport URL leads to errorStack Overflow