Yet one iteration of logging cleanup in connectors

- createResource is called just from ConnectionPool where is the exception processed too. Warning will be logged for each failure there, until retries exceed configured count of attempts. Then instead of warning it will throw an exception. - Removed also i18n properties, fixed messages, unused dumpPoolStatus Signed-off-by: David Matějček <david.matejcek@omnifish.ee>
eclipse-ee4j · Apr 9, 2023 · fb97501 · fb97501
1 parent 08d7fc5
commit fb97501
Show file tree

Hide file tree

Showing 6 changed files with 179 additions and 294 deletions.
diff --git a/...n/java/com/sun/enterprise/connectors/service/ConnectorConnectionPoolAdminServiceImpl.java b/...n/java/com/sun/enterprise/connectors/service/ConnectorConnectionPoolAdminServiceImpl.java
@@ -1087,11 +1087,7 @@ public boolean flushConnectionPool(PoolInfo poolInfo) throws ConnectorRuntimeExc
         try {
             return poolMgr.flushConnectionPool(poolInfo);
         } catch (PoolingException ex) {
-            ConnectorRuntimeException e = new ConnectorRuntimeException(
-                ex.getLocalizedMessage() + ". Please check the server.log for more details.");
-            e.initCause(ex);
-            throw e;
-
+            throw new ConnectorRuntimeException("Flushing the connection pool " + poolInfo.getName() + " failed.", ex);
         }
     }