[3.0] Make sure to close the connection in case of error

hibernate-reactive-core/src/main/java/org/hibernate/reactive/logging/impl/Log.java

@@ -270,6 +270,10 @@ public interface Log extends BasicLogger {
 	@Message(id = 84, value = "The application requested a JDBC connection, but Hibernate Reactive doesn't use JDBC. This could be caused by a bug or the use of an unsupported feature in Hibernate Reactive")
 	SQLException notUsingJdbc();
 
+	@LogMessage(level = ERROR)
+	@Message(id = 86, value = "Error closing reactive connection")
+	void errorClosingConnection(@Cause Throwable throwable);
+
 	// Same method that exists in CoreMessageLogger
 	@LogMessage(level = WARN)
 	@Message(id = 104, value = "firstResult/maxResults specified with collection fetch; applying in memory!" )
@@ -328,5 +332,4 @@ public interface Log extends BasicLogger {
 			" This is probably due to an operation failing fast due to the transaction being marked for rollback.",
 			id = 520)
 	void jdbcExceptionThrownWithTransactionRolledBack(@Cause JDBCException e);
-
 }

hibernate-reactive-core/src/main/java/org/hibernate/reactive/session/impl/ReactiveSessionImpl.java

@@ -1700,7 +1700,23 @@ public void close() throws HibernateException {
 
 	@Override
 	public CompletionStage<Void> reactiveClose() {
-		super.close();
+		try {
+			super.close();
+			return closeConnection();
+		}
+		catch (RuntimeException e) {
+			return closeConnection()
+					.handle( CompletionStages::handle )
+					.thenCompose( closeConnectionHandler -> {
+						if ( closeConnectionHandler.hasFailed() ) {
+							LOG.errorClosingConnection( closeConnectionHandler.getThrowable() );
+						}
+						return failedFuture( e );
+					} );
+		}
+	}
+
+	private CompletionStage<Void> closeConnection() {
 		return reactiveConnection != null
 				? reactiveConnection.close()
 				: voidFuture();