php-enqueue/enqueue-dev

Filesystem transport: The "failed" receiver does not support listing or showing specific messages

Hubbitus opened this issue · 7 comments

Hubbitus commented

Hello.

I've setup failed transport as local filesystem write:
config/packages/messenger.yaml:

framework:
    messenger:
        # Uncomment this (and the failed transport below) to send failed messages to this transport for later handling.
        failure_transport: failed

        transports:
            async_kafka:
               ...
            failed:
                dsn: 'enqueue://enqueue_file?topic[name]=fails'

        routing:
            # Route your messages to the transports
            'App\DAO\DemoNotification': [ async_kafka ]

config/packages/enqueue.yaml:

enqueue:
    enqueue_file:
        transport:
            dsn: 'file://'
            path: '%kernel.project_dir%/var/queue/kafka.mirror'

Together with configuring custom middleware by symfony/symfony#35521 I be able to send messages into failed queues when Kafka is not available.

Meantime I can't read that:

bin/console messenger:failed:show
[critical] Error thrown while running command "messenger:failed:show". Message: "The "failed" receiver does not support listing or showing specific messages."
Hubbitus commented

I am also willing to store such messages into some human-readable format, e.g. into JSONLines files to see that content and process. But did not find such options also. Is it possible?

makasim commented

Please, open the issue on messenger or adapter repo

makasim commented

I am also willing to store such messages into some human-readable format, e.g. into JSONLines files to see that content and process. But did not find such options also. Is it possible?

you can take fs transport as a base and implement your own version

Hubbitus commented

Please, open the issue on messenger or adapter repo

Sorry, but is not there just should be implemented MessageCountAwareInterface, ListableReceiverInterface?

Similar to the said alekitto/messenger-extra#13

Steveb-p commented

@Hubbitus Those are Symfony interfaces. They cannot be added to base class here, because they would force everyone to install that Symfony dependency as well.

Adding those is ultimately the task of the adapter.

  • 👍1
Hubbitus commented

@Steveb-p, @msheakoski, could you please point me where the right place to report such an issue? Which repo?