GitHub user nsk-dvlpr added a comment to the discussion: Grails 7: Transaction/locking behaviour changes?
Hi @jdaugherty Thanks for your quick reply. * We are already using HikariCP on the Grails 6.x version and the config between the upgrades is the same (including `maximumPoolSize`). We only bumped the HikariCP version from 4.0.3 to 6.x as part of the upgrade. * We can still see the issue on 7.0.9 (having your latest fix) It doesn't seem that the problem is caused by the Hikari itself. Seems that the connections are not released in time by the transactions holding them up waiting for a row lock, so likely something has changed in that area. I remember seeing a similar bug during the upgrade from Grails 3.x to 4.x when `deleteAll()` started locking the whole table instead of a single row and we had to change it to delete each entry by its PK, but doesn't seem to be the case here. Is there anything else you can think of that has changed between 6.x and 7.x that we can investigate? Thanks GitHub link: https://github.com/apache/grails-core/discussions/15515#discussioncomment-16196059 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
