You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
paxuclus
added a commit
to paxuclus/JobQueue.RabbitMQ
that referenced
this issue
Mar 14, 2022
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 to1
.Expected behavior:
If no message is found in time, the RabbitQueue should return
null
as stated in the PHPDoc of the QueueInterface (See here).The text was updated successfully, but these errors were encountered: