Skip to content

[symfony bundle] EnqueueExtension. Transport factory with such name already added. Name stomp #383

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

Closed
TheRatG opened this issue Feb 28, 2018 · 3 comments · Fixed by #388
Closed
Labels

Comments

@TheRatG
Copy link

TheRatG commented Feb 28, 2018

Q A
Issue Type Bug
Version 0.8.21
Local Machine OS Mac Os Darwin
Remote Machine OS Ubuntu

Description

When using ./bin/console debug:config EnqueueBundle in production mode I am getting this error

In EnqueueExtension.php line 48:
  Transport factory with such name already added. Name stomp  

Steps to reproduce

composer create-project symfony/skeleton enqueue
cd enqueue
composer config extra.symfony.allow-contrib true
composer require enqueue/enqueue-bundle enqueue/amqp-lib
perl -pi -w -e 's/APP_ENV=dev/APP_ENV=prod/g;' .env
./bin/console c:cl
./bin/console debug:config EnqueueBundle

Output log

./bin/console debug:config EnqueueBundle -vvv
2018-02-28T09:22:15+00:00 [error] Error thrown while running command "debug:config EnqueueBundle -vvv". Message: "Transport factory with such name already added. Name stomp"
2018-02-28T09:22:15+00:00 [debug] Command "debug:config EnqueueBundle -vvv" exited with code "1"

In EnqueueExtension.php line 48:
  [LogicException]                                            
  Transport factory with such name already added. Name stomp  
                                                              
Exception trace:
 Enqueue\Bundle\DependencyInjection\EnqueueExtension->addTransportFactory() at /Users/v.pak/www/enqueue/vendor/enqueue/enqueue-bundle/EnqueueBundle.php:60
@makasim makasim added the bug label Feb 28, 2018
@neandher
Copy link

When this happen, just run: cache:clear and works for me.

@DamienHarper
Copy link
Contributor

@neandher Sure it does the trick but it's definitely not a solution in the end!
I have all my current deployments (using deployer) fail because in the process they have to run a cache:clear which fails because of this issue and this failure stops the whole deployment process...

@neandher
Copy link

@DamienHarper You're right.

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.

4 participants