TYPO3 Forger
  • Dashboard
  • Get involved
  • Reviews
    Overview Ready for review Work in progress Needs action Needs review Needs verification Needs rebase Negative votes Reviewed and verified Ready to merge
  • Issues
    Stale issues Possible duplicates By category By month
  • Sprints
    Overview Initiatives TYPO3 Core Review board
  • Tools
    Backports ReST helper
  • Help
  • Search
  • Login
Esc

Words find the open ones, a number the issue and the change with it.

  1. Issues
  2. #107032
Issue Bug Closed

#107032AsMessageHandler attribute property fromTransport is ignored

Oliver Eglseder 07/03/25, 21:14 updated 08/11/26, 08:46

Open in Forge Comment in Forge

Description

This make it virtually impossible to implement an async send/receiver setup.
The implementation of symfony/messenger should at least support the separation of busses and transports. Also, TYPO3 should not register a default catchall router ('*') on its own.

Reviews 5

  • main 94834[FEATURE] Maintain DB connections in Messenger workers Related to this issue Merged Stefan Bürk CR +2 V +2 messenger Expert +1084 −0 10/08/26, 12:22
  • 14.3 95063[BUGFIX] Honour `AsMessageHandler::$fromTransport` property Resolves this issue Merged Stefan Bürk CR +2 V +2 → main messenger-14.3 Hard +613 −13 08/02/26, 12:14
  • main 94833[BUGFIX] Honour `AsMessageHandler::$fromTransport` property Resolves this issue Merged Stefan Bürk CR +2 V +2 → 14.3 messenger Hard +613 −13 08/02/26, 12:14
  • 14.3 95008[BUGFIX] Treat Messenger wildcard route as fallback Related to this issue Merged Stefan Bürk CR +2 V +2 → main messenger-14.3 Hard +667 −24 07/30/26, 06:24
  • main 94829[BUGFIX] Treat Messenger wildcard route as fallback Related to this issue Merged Stefan Bürk CR +2 V +2 → 14.3 messenger Hard +667 −24 07/30/26, 06:24
Author
Oliver Eglseder
Priority
Should have
Category
System/Bootstrap/Configuration
TYPO3 version
13
PHP version
8.3
© 2026 TYPO3 GmbH.
  • API
  • Privacy Policy
  • Legal Notice
  • Feedback