8000 [Messenger] stats command fails for Beanstalked transport · Issue #53526 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content
[Messenger] stats command fails for Beanstalked transport #53526
Closed
@eminjk

Description

@eminjk

Symfony version(s) affected

6.4

Description

command messenger:stats fails with an error when it needs to get data from Beanstalkd transport and the tube is empty


In Connection.php line 187:
                             
  Server reported NOT_FOUND  
                             

In YamlResponseParser.php line 39:
                             
  Server reported NOT_FOUND  
                             

How to reproduce

for the new tube:

  1. setup Beanstalkd
  2. run messenger:stats command

similar for an emptied queue:

  1. setup Beanstalkd
  2. dispatch some messages
  3. process them all
  4. run messenger:stats command

Possible Solution

The command works fine when there are still messages in the queue. Apparently, when the tube (queue in Beanstalkd) is empty, Beanstalkd clears all data about the tube. Connection returns exception (code "Server reported NOT_FOUND") which is just forwarded in
( symfony/beanstalkd-messenger/Transport/Connection.php:185 )

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0