-
Notifications
You must be signed in to change notification settings - Fork 212
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
[ECP-8518] Unset amqp in config to use default queue connection #2654
Conversation
@factorin-j I have encountered an issue related to the adyen.notification consumer in Magento 2, where it attempts to use an amqp connection even though we have configured it to use cron. I came across a pull request that seems to address this problem. Could you please provide an update on the development status of this PR? Is there a planned timeline for merging and releasing this fix? We are looking forward to a resolution to improve our current setup. Thank you! |
@andreusala, sorry for the delayed response. I'm not certain about the timeline for this PR. We might need to coordinate with @candemiralp on this matter. In the meantime, you can refer to this comment #2031 (comment) as an initial fix if you're encountering the same issue. |
- remove amqp in queue xml config to use default (db) if amqp service is not installed. - include additional admin message when using 'queue' notification processing - add unit tests
This reverts commit 495ec49.
Hello @factorin-j, Thank you for your contribution to solve this bug. This PR will be released soon. Best Regards, |
Description
Tested scenarios
bin/magento setup:install
with opensearch/elasticsearch onlybin/magento setup:install
with--amqp-*
options included (RabbitMQ installed).Fixes #2031