Skip to content

Fixed the order of Doctrine middleware in Messenger component #12357

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 23, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions messenger.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1376,11 +1376,6 @@ may want to use:
buses:
command_bus:
middleware:
# wraps all handlers in a single Doctrine transaction
# handlers do not need to call flush() and an error
# in any handler will cause a rollback
- doctrine_transaction

# each time a message is handled, the Doctrine connection
# is "pinged" and reconnected if it's closed. Useful
# if your workers run for a long time and the database
Expand All @@ -1392,6 +1387,11 @@ may want to use:
# instead of keeping them open forever
- doctrine_close_connection

# wraps all handlers in a single Doctrine transaction
# handlers do not need to call flush() and an error
# in any handler will cause a rollback
- doctrine_transaction

# or pass a different entity manager to any
#- doctrine_transaction: ['custom']

Expand Down