We have some situations where we expect connection states changes caused by exception and we catch and process the exceptions accordingly (never log them, because they are normal operational state). However, HikariCP still logs them (and fills our logs).
Would it be possible to add a switch that suppresses logging the exception (the "WARN - Connection broken because of ..." is fine, just the full exception stack trace is too much)?
the eviction code at https://github.com/brettwooldridge/HikariCP/blob/dev/src/main/java/com/zaxxer/hikari/pool/ProxyConnection.java#L178 logs an exception that caused a connection to be marked as bad but then rethrows it.
We have some situations where we expect connection states changes caused by exception and we catch and process the exceptions accordingly (never log them, because they are normal operational state). However, HikariCP still logs them (and fills our logs).
Would it be possible to add a switch that suppresses logging the exception (the "WARN - Connection broken because of ..." is fine, just the full exception stack trace is too much)?