update log level to debug

[GertDE]

This prevents unnecessary log spam in production environments.

[brettwooldridge]

@GertDE Hmmmm, why is this happening in production? This is definitely not "expected" behaviour from the perspective of the pool.

[GertDE]

@brettwooldridge I'm using Spring and catching QueryTimeoutException (query is interrupted after 1 second) in my application, but HikariCP still logs a warning, so i can`t grep for real exceptions.

[brettwooldridge]

@GertDE What about this solution?

[GertDE]

@brettwooldridge I've addressed this locally by raising the logging level to ERROR:
logging.level.com.zaxxer.hikari.pool.ProxyConnection=ERROR
In general, I consider it bad practice to log exceptions that aren't actually thrown, as it creates noise in the logs and makes real issues harder to identify. Could you share the reasoning behind logging an exception in this case? Wouldn't the DEBUG level be more appropriate for analytical purposes?

[brettwooldridge]

@GertDE It is best practice that exceptions that are eaten must be logged.

https://javanexus.com/blog/handling-swallowed-exceptions-java-guide

[GertDE]

Yes, that's correct, but you're handling the exception and rethrowing it, so it's not a swallowed exception.