bin/console messenger:consume-messages amqp in PROD env using amqp_lib transport about messenger-enqueue-transport

[wexotht]

@sroze a fix for this would be nice. Still an issue meaning a lot of manual work on production environments upon setup

[srigi]

+1 to this. I'm also having problems running my consumers in production ENV. I get similar excp as @LPodolski NOT_FOUND - no queue 'transactional-emails' in vhost '/'.

There is no clear way how to pre-create queues in prod ENV. Only solution is to enable APP_DEBUG. That is just unacceptable in prod.

[salletti]

The problem is that the queue is automatically created only when debug is active, like in dev.

File: vendor/enqueue/messenger-adapter/QueueInteropTransport.php

if ($this->debug) {
      $this->contextManager->ensureExists($destination);
}

So maybe in prod you must use the command for create manually the queue:

https://github.com/php-enqueue/enqueue-dev/blob/master/docs/bundle/cli_commands.md#enqueuesetup-broker

[makasim]

The linked command has nothing to do with messenger

It is part of enqueue client library

[salletti]

In my opinion the problem concerns php enqueue library.

[makasim]

It has nothing to do with Enqueue itself, It gives you full control over what you can do.

The problem lies in this messenger adapter, its implementation.
In fact, the implementation of this adapter follows the same logic of the official amqp ext transport bundled with symfony.

https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Messenger/Transport/AmqpExt/Connection.php#L126

[StarGuardian]

I bumped into the same issue and found following workaround. Wrote my own transport factory (It is basically the same except one line):
`class AmqpTransportFactory implements TransportFactoryInterface
{
private $encoder;
private $decoder;
private $debug;

public function __construct(EncoderInterface $encoder, DecoderInterface $decoder, bool $debug)
{
    $this->encoder = $encoder;
    $this->decoder = $decoder;
    $this->debug = $debug;
}

public function createTransport(string $dsn, array $options): TransportInterface
{
    return new AmqpTransport($this->encoder, $this->decoder, $this->createConnection($dsn, $options));
}

public function supports(string $dsn, array $options): bool
{
    return 0 === strpos($dsn, 'amqp://');
}

protected function createConnection(string $dsn, array $options) {
    $connection = Connection::fromDsn($dsn, $options, $this->debug);
    $connection->setup(); // <--- Workaround is here

    return $connection;
}

}`

Then I override messenger.transport.ampq.factory definition in my services.yml. It works well!

[tdsullivan]

I know this is an old thread, and this isn't an optimal solution, but for anyone looking for a quick workaround, adding the following to your services definition file, to default the 'debug' argument to true, seems to do the trick.

    enqueue.messenger_transport.factory:
        class: 'Enqueue\MessengerAdapter\QueueInteropTransportFactory'
        arguments:
            - '@messenger.default_serializer'
            - '@enqueue.locator'
            - true
        tags: ['messenger.transport_factory']

[tdsullivan]

Also, regarding the comments above about the official amqp ext transport, that is bundled with symfony messenger, handling this the same way, this behaviour was changed in version 4.3.

Using AMQP auto-setup in all cases, not just in debug #30579