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
Recently I started to see connection timeout errors : Connection is not available, request timed out after 500ms . I already verified that there is no connection leak. After some trial and error, I increased the pool size to 22 and that reduced the number of errors. But I still see some now and then.
To investigate it further, I now create a thread dump whenever this exception is thrown. However, it would be great if I could also identify the threads that hold the connection at that time.
Is it possible to log the thread name/ids that are holding the connection at any moment? I see that when I enable leakDetection, it logs the thread name: Connection leak detection triggered for xxxx on thread xxxx, stack trace follows . But I did not find a way to get this information without triggering leakDetection .
The text was updated successfully, but these errors were encountered:
@brettwooldridge My application has the following Hikari configuration:
Recently I started to see connection timeout errors :
Connection is not available, request timed out after 500ms
. I already verified that there is no connection leak. After some trial and error, I increased the pool size to 22 and that reduced the number of errors. But I still see some now and then.To investigate it further, I now create a thread dump whenever this exception is thrown. However, it would be great if I could also identify the threads that hold the connection at that time.
Is it possible to log the thread name/ids that are holding the connection at any moment? I see that when I enable
leakDetection
, it logs the thread name:Connection leak detection triggered for xxxx on thread xxxx, stack trace follows
. But I did not find a way to get this information without triggeringleakDetection
.The text was updated successfully, but these errors were encountered: