You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I am using Audit Logging 4.0.3 with Grails 5.2.4. I would like to confirm the transactional behavior. The Audit Logging documentation seems to suggest that if there is an existing transaction the plugin will use that transaction for the audit events. However, looking at my Hibernate logs, it looks like the plugin is starting a separate transaction just for the audit events.
Is there anything I can do to have it use the existing transaction?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello! I am using Audit Logging 4.0.3 with Grails 5.2.4. I would like to confirm the transactional behavior. The Audit Logging documentation seems to suggest that if there is an existing transaction the plugin will use that transaction for the audit events. However, looking at my Hibernate logs, it looks like the plugin is starting a separate transaction just for the audit events.
Is there anything I can do to have it use the existing transaction?
Any help would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions