-
Notifications
You must be signed in to change notification settings - Fork 42
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
Update Agroal to 2.4 #147
Update Agroal to 2.4 #147
Conversation
@graben maybe, although the |
I'm actually thinking it could be something like timing between parallel threads. But this is currently only a hypothesis. |
@barreiro : Setting the wait timeout to a larger value helps, but it needs closing the complete pool of 10 Connections? I think something is going wrong.
|
that message means that the connection wrappers are still open on commit and Agroal is closing them for you (to prevent concurrent calls with commit, and eventual leaks). they should be closed beforehand. because now the recovery is executed from the connections on the pool, there can be more pressure on the number of available connections. (or can be an issue too, of course) |
Setting |
I'll have a look at the test case later today. |
Setting logging output to DEBUG. It seems test thread and recovery thread are struggling with the same connection. Recovery succeeds after a new connection is created because recovery thread locks the former one.
|
@barreiro : I just did a little "dirty" experiment. Instead of calling |
Doing a Got it working with PostgreSQL, SQL Server and Derby. Needs some "hack" because databases react different with locking tables after the crash letting IMHO, actually no bug in Agroal, but stupid behaviour of H2 the test has to deal with. |
@barreiro: Maybe a regression in latest Agroal version? I'll have a look into the test case either way.