Soften ConnId errors logging (part of MID-5937)

Evolveum · Nov 23, 2019 · df5b4b9 · df5b4b9
1 parent 95fb4ed
commit df5b4b9
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/...l-connid/src/main/java/com/evolveum/midpoint/provisioning/ucf/impl/connid/ConnIdUtil.java b/...l-connid/src/main/java/com/evolveum/midpoint/provisioning/ucf/impl/connid/ConnIdUtil.java
@@ -132,8 +132,10 @@ static Throwable processConnIdException(Throwable connIdException, String desc,
             throw new IllegalArgumentException("Null exception while processing ConnId exception ");
         }
 
-        LOGGER.error("ConnId Exception {} in {}: {}", connIdException.getClass().getName(),
-                desc, connIdException.getMessage(), connIdException);
+        // We intentionally do not use LOGGER.error here, to avoid dumping the stack unless the DEBUG logging is set.
+        // This is because ConnID errors often get handled in upper layers. See also MID-5937.
+        LoggingUtils.logExceptionAsWarning(LOGGER, "Got ConnId exception (might be handled by upper layers later) {} in {}: {}",
+                connIdException, connIdException.getClass().getName(), desc, connIdException.getMessage());
 
         if (connIdException instanceof RemoteWrappedException) {
             // brutal hack, for now