We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to the documentation, it says that usually you do not need to catch exceptions in the message processor.
Currently, if an exception occurs, the consumer process exits completely instead of logging an error.
I can wrap my processors in a try/catch, but it would be a nice improvement to have the consumer automatically catch exceptions and log them.
The text was updated successfully, but these errors were encountered:
That's expected behavior, a consumer has to fail fast for various reasons.
We discussed that several times some time ago and came to a conclusion that this is the right behavior.
Sorry, something went wrong.
Ok, that makes sense. Maybe the documentation could be a little clearer on that?
[doc][skip ci] Add processor examples, notes on exception and more.
157feae
fixes #240
ace9ebe
02ff986
fixes php-enqueue/enqueue-dev#240
Successfully merging a pull request may close this issue.
According to the documentation, it says that usually you do not need to catch exceptions in the message processor.
Currently, if an exception occurs, the consumer process exits completely instead of logging an error.
I can wrap my processors in a try/catch, but it would be a nice improvement to have the consumer automatically catch exceptions and log them.
The text was updated successfully, but these errors were encountered: