HHH-8210 JdbcCoordinatorImpl logs excessive warnings with some

connection pools

Author: brmeyer

hibernate-core/src/main/java/org/hibernate/engine/jdbc/internal/JdbcCoordinatorImpl.java

@@ -381,7 +381,9 @@ public void register(ResultSet resultSet, Statement statement) {
 			}
 		}
 		if ( statement != null ) {
-			if ( LOG.isEnabled( Level.WARN ) && !xref.containsKey( statement ) ) {
+			// Keep this at DEBUG level, rather than warn.  Numerous connection pool implementations can return a
+			// proxy/wrapper around the JDBC Statement, causing excessive logging here.  See HHH-8210.
+			if ( LOG.isEnabled( Level.DEBUG ) && !xref.containsKey( statement ) ) {
 				LOG.unregisteredStatement();
 			}
 			Set<ResultSet> resultSets = xref.get( statement );
@@ -407,7 +409,9 @@ public void release(ResultSet resultSet) {
 			throw exceptionHelper.convert( e, "unable to access statement from resultset" );
 		}
 		if ( statement != null ) {
-			if ( LOG.isEnabled( Level.WARN ) && !xref.containsKey( statement ) ) {
+			// Keep this at DEBUG level, rather than warn.  Numerous connection pool implementations can return a
+			// proxy/wrapper around the JDBC Statement, causing excessive logging here.  See HHH-8210.
+			if ( LOG.isEnabled( Level.DEBUG ) && !xref.containsKey( statement ) ) {
 				LOG.unregisteredStatement();
 			}
 			Set<ResultSet> resultSets = xref.get( statement );

hibernate-core/src/main/java/org/hibernate/internal/CoreMessageLogger.java

@@ -1342,7 +1342,9 @@ void unableToWriteCachedFile(String path,
 	@Message(value = "ResultSet had no statement associated with it, but was not yet registered", id = 386)
 	void unregisteredResultSetWithoutStatement();
 
-	@LogMessage(level = WARN)
+	// Keep this at DEBUG level, rather than warn.  Numerous connection pool implementations can return a
+	// proxy/wrapper around the JDBC Statement, causing excessive logging here.  See HHH-8210.
+	@LogMessage(level = DEBUG)
 	@Message(value = "ResultSet's statement was not registered", id = 387)
 	void unregisteredStatement();