After executing some queries the connection to the MSSQL server gets lost, I only receive this error: Unable to open connection:
Only server restart helps in this case.
Activity
Show:
Michael Born @ OrtusJanuary 15, 2025 at 3:33 PM
But as far as actually solving the connection leak issue, we have more debugging to do.
Can you enable boxlang’s debug mode (or ensure it IS enabled), then look for any DEBUG logs from Hikari? I am most interested in seeing leak detection logs or pool statistics.
Also, please upgrade to the latest snapshot. Luis just added leak detection config defaults 2 days ago, so you’ll want to be sure you’re on this version or later to enable Hikari’s leak detection logs.
Michael Born @ OrtusJanuary 15, 2025 at 3:26 PM
@Harry Klein You can bump your connection limit up to at least increase the amount of time you have before the pool fills.
Set maxConnections in your datasource properties to 100 , 1000, or more.
Harry KleinJanuary 15, 2025 at 2:50 PM
@Doohickey Still having this issue which makes it almost impossible to work. I have to restart the server every 3-5 minutes. The last error info I had was: HikariPool-1 - Connection is not available, request timed out after 1001ms (total=15, active=15, idle=0, waiting=1)
Harry KleinJanuary 11, 2025 at 11:12 AM
Edited
@Doohickey Sorry, but I got the “Unable to open connection“ error again - this issue is still open …
Michael Born @ OrtusJanuary 8, 2025 at 3:39 PM
Oh, that’s fantastic news then @Harry Klein . Thank you, and let us know if you see any more issues.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
After executing some queries the connection to the MSSQL server gets lost, I only receive this error:
Unable to open connection:
Only server restart helps in this case.