Closed shubaivan closed 3 years ago
First off... Your library config is the wrong one.
As of version 10 the library internals have changed drastically.
The library was a library that did "almost" everything from the perspective view of RabbitMQ. (how rabbitMQ handles queuing) As of version 10: the point of view has been changed/transferred to follow the Laravel idea/perspective of queuing.
The library now is more inline with Laravel's QueueAPI and is (by default) now a drop-in replacement (driver), so you can also use RabbitMQ as message-broker. It also has a couple of features that are specific to RabbitMQ. so you can benefit from most features rabbitMQ holds.
I'm closing the issue ;) I don't think you have a bug, rather then a configuration error.
But when your'e convinced it is a bug, please let us know.
Laravel with RabbitMQ, queue not shown information about exist jobs and has state - live instead idle or runnig. I guess maybe some in cofiguration queue or rabbit mq version. I used docker compose
This is what I have in UI rabbitmq
this is my dockerfile for rabbit
and docker compose
my composer in application
my queue conf
my .env
and what I hade in rabbitmq UI, without 'Messages' info, how many jobs ready
but I expected 'idle' state with ready counter for jobs if I did not executed some worker and expect 'running' state when I executed some worker.
this is how I send job in my connection in chanel
Steps To Reproduce
What steps needed, to reproduce this bug.
Current behavior
jobs are created and executed if execute
artisan rabbitmq:consume rabbitmq --queue=queue_handling_email
but tab rabbitmq UI tabsMessages | Message rates
not presented and queue has state liveExpected behavior
`Messages | Message rates tabs should be present adn sate should be idle or running if worker was execute