Open buehlefs opened 8 months ago
I can still reproduce this in Ballerina 2201.9.0 @dsplayerX is this issue being worked on?
Hi @buehlefs,
We believe this issue arose from the locking implemented to make transactions concurrent safe in this PR. The delayed release of these locks and concurrent requests could be causing the Hikari pool to be exhausted. We're currently searching for a method to address this issue.
Description
Successfull transactions can exhaust the HikariPool of connections when they are executed concurrently. The issue does not appear when the transactions are run sequentially in a while-true loop in a single thread. Later transactions will then result in stacktraces like this after a long timeout:
Steps to Reproduce
The issue should be reproducible with the test code in issue #41281 All transactions must commit normally to make the issue more likely to occur.
Affected Version(s)
Ballerina 2201.8.5 (Swan Lake Update 8) Ballerina 2201.8.4
OS, DB, other environment details and versions
OS: Ubuntu 20.04 running inside WSL2
JDBC Connector used:
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response