-
Notifications
You must be signed in to change notification settings - Fork 422
[Bug] Artisan command keep running even if the consumer has exception with Broken Pipe #421
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
Comments
This behavior also is happening with Laravel Horizon. If something happens to the connection between the queue workers and the Rabbit server, my logs start filling up with:
and
messages. Terminating Horizon and letting supervisor or systemd restart the processes clears the errors (assuming connectivity has been reestablished between the queue workers and RabbitMQ). |
Full stack trace:
The actual errors are happening in the php-amqplib library, is this a bug that should be raised there or do we need to add better error handling in this package for the Exceptions thrown by php-amqplib? |
Hello, @bandgeekndb Did you manage to solve it? |
We are observing the same problem, which also appears related to report #436 . |
@acosta-edgar Thanks for sharing this info, that's definitely helpful! I'm not around next week, but when I get back, I'll fork this and see if I can add some connection recovery handling like you mentioned. If I can, I'll open a PR and see what the dev thinks! |
Should be fixed by #457 |
Describe the bug
Whenever there's error on Connection and throw exception
php artisan rabbitmq:consume
doesn't stop or terminate. As the command is running, the monitoring tools like Supervisor doesn't know the status of consumer and consumers are not restarted.Meanwhile this exception the there's no consumer on queue but Supervisor shows the process is running
Steps To Reproduce
Start the command
php artisan rabbitmq:consume
and externally trigger Broken Pipe or connectionExpected behavior
Whenever there's broken pipe exception, the artisan command should have been stopped or terminated
The text was updated successfully, but these errors were encountered: