Avoid opening a transaction for event externalization #859
Assignees
Labels
Milestone
Comments
odrotbohm
added a commit
that referenced
this issue
Oct 6, 2024
We now use the ability to override transaction propagation introduce for GH-858 to tweak the application module listener declaration on DelegatingEventListener so that we do not create a transaction by default. This avoids a database connection being acquired as the listener is very likely to interact with a non-transactional resource anyway.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
DelegatingEventExternalizercurrently uses@ApplicationModuleListenerto asynchronously publish events to a broker on transaction commit. That said,@AMLcreates a transaction itself, which is unnecessary in this case as the listener solely interacts with infrastructure that's not transactional in the first place.To avoid a connection unnecessarily being acquired, we should flip the transaction propagation to
SUPPORTS, i.e., not actively creating a transaction but simply participating in one in case some infrastructure still creates one.The text was updated successfully, but these errors were encountered: