Closed pimjansen closed 5 years ago
I noticed that it also happens on the REENQUEUE return type. Works well for the ACK and REJECT
I get the same exception after few minutes with no messages, even with ACK.
`LogicException: Processor was not found. processorName: "Enqueue\Consumption\CallbackProcessor5cdd92fa1c131" in /var/www/html/protected/vendors/enqueue/enqueue/ArrayProcessorRegistry.php:33 Stack trace:
don't bother with my problem, I'm not going to use enqueue ... just not ready/stable jet. You should definitely improve your documentation ... "basic" would be euphemism.
Same problem as @dmlang , It seems that it'll randomly throw that error after a while.
I'm using the redis client
EDIT: Seems like it works fine when using amqp-ext
possibly a bug. needs PR
This is a bug but you close it?
It is stale. Nobody works on it. What is the reason keeping it open? What for?
To keep bugs and limitations of the package in plain sight. Nobody looks at CLOSED issues when reviewing a github repo.
Then the tracker is overflowed with open issues making it really hard to find relative stuff. I am fine keeping them open for some time or if some work is in progress.
I have the same issue
Having the same issue too!
There is a 3rd parameter $processorName
on bindCommand
method.
Use it to avoid hashed processor's name.
There is a 3rd parameter
$processorName
onbindCommand
method.
Adding php-enqueue to slim, this error came up - it's adding a suffix on the class name and I am not quite sure what it is for. Adding the class name as the processor fixes the problem.
I've been having this problem, and couldn't figure out why the processor suffix keeps coming up, even after following the above solutions.
Finally I went into my rabbitmqctl and purge all queues, and it works !
I guessed sth might have went wrong with my rabbitmq from previous testing.
Hi,
Im trying out enqueue-dev with a basic setup within laravel. All works fine however i would like to decouple it from the framework and use the provided client instead. Main reason is that i want plain json in my queues to also consume in other languages.
Im now pushing messages on the queue with below:
All works fine and in the end i indeed have a few messages on my queue. I also registered a simple listener like below which works fine:
The only problem hits that my consumer in this case is not returning a ACK. When start the consumer
php artisan enqueue:consume --setup-broker -vvv
initially it runs fine but when i try to run it again i get the error mentioned in the title. I do expect it to be possible though since technically my consumer crashes at this point by not returning an ACK and the message stays on the queue itself.The full stack