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

RabbitQueue throws AMQPTimeoutException after timeout with --exit-after #18

Closed
paxuclus opened this issue Mar 14, 2022 · 0 comments · Fixed by #19
Closed

RabbitQueue throws AMQPTimeoutException after timeout with --exit-after #18

paxuclus opened this issue Mar 14, 2022 · 0 comments · Fixed by #19

Comments

@paxuclus
Copy link
Contributor

The job:work command of the Flowpack.JobQueue.Common package supports the parameter --exit-after which allows to set a time limit after which the command exists.

If during that time no message is published to the RabbitMQ queue, an AMQPTimeoutException is thrown, setting the exit code of the job:work process to 1.

Expected behavior:
If no message is found in time, the RabbitQueue should return null as stated in the PHPDoc of the QueueInterface (See here).

paxuclus added a commit to paxuclus/JobQueue.RabbitMQ that referenced this issue Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant