Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Invalid option(s) "queue_name" passed to Messenger transport #239

Closed
studio1gmbh-pimcore opened this issue Sep 4, 2023 · 1 comment · Fixed by #240
Closed

[Bug]: Invalid option(s) "queue_name" passed to Messenger transport #239

studio1gmbh-pimcore opened this issue Sep 4, 2023 · 1 comment · Fixed by #240
Labels
Milestone

Comments

@studio1gmbh-pimcore
Copy link
Contributor

Expected behavior

Alternative messenger transport (redis, amqp, etc.) should be supported.

Actual behavior

Alternative messengers are not supported as the configuration cannot be correctly changed.

Steps to reproduce

Switch the default transport (doctrine) to alternative transport

framework:
    messenger:
        transports:
            pimcore_index_queues:
                dsn: '%env(AMQP_DSN)%/%2f/pimcore_index_queues'

Result:

[Symfony\Component\Messenger\Exception\LogicException] Invalid option(s) "queue_name" passed to the AMQP Messenger transport.

The option queue_name is still present in the default config, although it is no longer supported by different transports.

framework:
messenger:
transports:
pimcore_index_queues:
dsn: 'doctrine://default'
options:
queue_name: pimcore_index_queues

Issue widely known in the core and other bundles. We are asking ourself, why it is not fixed here yet?

See:
pimcore/data-importer#226
pimcore/pimcore#11355
https://github.com/pimcore/portal-engine/pull/168

@dvesh3
Copy link
Contributor

dvesh3 commented Sep 12, 2023

Fixed by #240

@dvesh3 dvesh3 closed this as completed Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants