#106261Add --time-limit option to messenger:consume
Description
The original Symfony messenger (https://symfony.com/doc/current/messenger.html) has an option —time-limit to specify, how long the messenger:consume service should run before shuts down automatically.
This is useful for environments, where it is not possible to create a system service which re-starts automatically, e.g. in shared-hosting environments (or on all other servers without root access).
In this case it would be nice, if the messenger:consume could be triggered regularly e.g. by the Scheduler (The Scheduler already can be triggered regularly by external HTTP Cron request).
For example: Lets say, the messenger command is scheduled with **/5 * * * ** and executes messenger:consume —time-limit=16200. So it runs for a bit, shuts down after 4,5 minutes and is restarted if the scheduler invokes the command again after the next 5 minutes passed.
Reviews 2
History 617
-
Oliver Hader changed status
NewAccepted <span data-processor="relativetime" data-value="2025-08-21T10:11:54+00:00" > 08/21/25, 10:11 </span> -
Oliver Hader commented <span data-processor="relativetime" data-value="2025-08-21T10:27:15+00:00" > 08/21/25, 10:27 </span>
Symfony uses their own event dispatcher, which allows dynamically added listeners.
Our TYPO3 is “static”, since we don’t allow that yet. Even
\TYPO3\CMS\Core\EventDispatcher\ListenerProvider::addListeneronly allows static service names, but no stateful-instances or closures. -
Oliver Hader commented <span data-processor="relativetime" data-value="2025-08-21T10:45:13+00:00" > 08/21/25, 10:45 </span>
With the current implementation in TYPO3,
ConsumeMessagesCommandwould have to be shared and would require a dedicatedConsumeMessagesCommand::handleWorkerRunningEvent(WorkerRunningEvent $event)which re-implements (our existing)StopWorkerOnTimeLimitListener.Thus, I’d suggest to finally allow dynamically adding event listeners.
-
Gerrit Code Review pushed patch set 1 for main to change 91451 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2025-11-08T15:46:43+00:00" > 11/08/25, 15:46 </span> -
Gerrit Code Review pushed patch set 1 for main to change 91452 <span data-processor="relativetime" data-value="2025-11-08T15:46:45+00:00" > 11/08/25, 15:46 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 91452 <span data-processor="relativetime" data-value="2025-11-08T15:47:37+00:00" > 11/08/25, 15:47 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 91452 <span data-processor="relativetime" data-value="2025-11-08T15:55:17+00:00" > 11/08/25, 15:55 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 91452 <span data-processor="relativetime" data-value="2025-11-08T16:14:37+00:00" > 11/08/25, 16:14 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 91452 <span data-processor="relativetime" data-value="2025-11-08T16:35:01+00:00" > 11/08/25, 16:35 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 91452 <span data-processor="relativetime" data-value="2025-11-08T16:47:40+00:00" > 11/08/25, 16:47 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 91452 <span data-processor="relativetime" data-value="2025-12-06T12:52:49+00:00" > 12/06/25, 12:52 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 91452 <span data-processor="relativetime" data-value="2025-12-06T12:59:07+00:00" > 12/06/25, 12:59 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 91452 <span data-processor="relativetime" data-value="2026-01-30T18:08:38+00:00" > 01/30/26, 18:08 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 91452 <span data-processor="relativetime" data-value="2026-01-30T18:16:10+00:00" > 01/30/26, 18:16 </span>
-
Sascha Nowak commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-02-27T17:25:09+00:00" > 02/27/26, 17:25 </span>Applied in changeset commit:99fc701d3f710f430824bbbdb039335211a1a18e.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T09:00:42+00:00" > 03/31/26, 09:00 </span>
reference to symfony: https://github.com/symfony/symfony/blob/329920dad4fbeabd44e844ccef3229baefae3c19/src/Symfony/Component/Messenger/Command/ConsumeMessagesCommand.php#L223