Hi, It looks like Connection#clearWarnings() is not called on the proxied jdbc connection when the connection is returned to the pool.
Is this something missing or that's a design choice ? In our use case : 1 - borrow a connection from the pool 2 - use it -> the driver set a SQLWarning on the connection 3 - return (close) the connection to the pool 4 - borrow a connection from the pool 5 - the connection still has the SQLWarning Benoit
