Review main Abandoned

96568[BUGFIX] Reconnect Doctrine messenger transport after lost connection

Benni Mack CR -2 V +1 Normal +144 −1 updated 10/20/26, 15:30

Commit message

The Doctrine messenger transport uses its own DBAL connection, created
by DoctrineTransportFactory outside of the ConnectionPool. It lives as
long as the PHP process, so in long-running processes such as
"scheduler:run" executing several tasks it can stay idle longer than
the server allows (MySQL's wait_timeout). The next dispatch then fails
with "MySQL server has gone away".

The worker middlewares added with #110227 only maintain ConnectionPool
connections while consuming messages, so they do not cover this
connection or the sending side.

The factory now returns a transport that closes the stale connection
and retries the send once when the connection was lost.

Review

  • Code review CR -2
    • Benni Mack -2
    • Simon Schaufelberger +1
  • Verified V +1
    • Simon Schaufelberger +1
    • core-ci +1 CI

Issues 2

Files 3

Review log 811

  1. Benni Mack uploaded patch set 1 10/09/26, 17:10

  2. core-ci voted on patch set 1 V -1 10/09/26, 17:41 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/110658

  3. Benni Mack uploaded patch set 2 V -1 10/09/26, 19:00

  4. core-ci voted on patch set 2 V +1 10/09/26, 19:09 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/110692

  5. Benni Mack updated the commit message in patch set 3 V +1 10/10/26, 09:59

  6. Benni Mack marked it ready for review 10/10/26, 09:59

  7. core-ci voted on patch set 3 V +1 10/10/26, 10:07 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/110787

  8. Simon Schaufelberger voted on patch set 3 CR +1 V +1 10/19/26, 21:29

  9. Benni Mack commented on patch set 3 CR -2 10/20/26, 06:47

    I need to run this in my real-life project first
  10. Benni Mack marked it work in progress 10/20/26, 06:47

  11. Benni Mack abandoned the change 10/20/26, 15:30

    I think we need a different approach