With --time-limit, does Symfony kill messenger consumers while a message is being handled?

I was worried about that, and it appears Symfony does not kill messenger consumers while a message is being handled, only after the message is handled.

This is true for all --limit, --memory-limit, --time-limit options.

Let’s look at the code of the messenger:consume command (source):

1// when --limit
2$this->eventDispatcher->addSubscriber(new StopWorkerOnMessageLimitListener($limit, $this->logger));
3
4// when --memory-limit
5$this->eventDispatcher->addSubscriber(new StopWorkerOnMemoryLimitListener($this->convertToBytes($memoryLimit), $this->logger));
6
7// when --time-limit
8$this->eventDispatcher->addSubscriber(new StopWorkerOnTimeLimitListener($timeLimit, $this->logger));

Subscirbers listen to the WorkerRunningEvent to stop the consumer (source):

 1class StopWorkerOnTimeLimitListener implements EventSubscriberInterface
 2{
 3    // ...
 4
 5    public function onWorkerRunning(WorkerRunningEvent $event): void
 6    {
 7        if ($this->endTime < microtime(true)) {
 8            $event->getWorker()->stop();
 9        }
10    }
11
12    public static function getSubscribedEvents(): array
13    {
14        return [
15            WorkerStartedEvent::class => 'onWorkerStarted',
16            WorkerRunningEvent::class => 'onWorkerRunning',
17        ];
18    }
19}

WorkerRunningEvent says (source):

Dispatched after the worker processed a message or didn't receive a message at all.

So, Symfony does not kill a message while it’s being processed; Good!