Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
bug #36449 [Messenger] Make sure redis transports are initialized cor…
…rectly (Seldaek) This PR was squashed before being merged into the 4.4 branch (closes #36449). Discussion ---------- [Messenger] Make sure redis transports are initialized correctly | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | | License | MIT Took me a while to figure out why my messages were dispatched/handled twice.. Turns out I had two messenger transports using the same dsn and the parsing was broken so they ended up both polling from a `""` stream, which caused them to both handle the messages (I think). Below my config, note the trailing slash in the dsn was the root cause of the issue, but I don't think it's that unreasonable. ``` .env: MESSENGER_TRANSPORT_DSN=redis://localhost:6379/?dbindex=3 messenger.yml: async_urgent: dsn: '%env(MESSENGER_TRANSPORT_DSN)%' options: group: async_urgent stream: messages_urgent async: dsn: '%env(MESSENGER_TRANSPORT_DSN)%' options: group: async stream: messages ``` Commits ------- 68b3b89 [Messenger] Make sure redis transports are initialized correctly
- Loading branch information