KNOX-1324 - Remote Configuration Monitor should not log stacktrace when client is...
authorPhil Zampino <pzampino@apache.org>
Fri, 18 May 2018 14:50:52 +0000 (10:50 -0400)
committerPhil Zampino <pzampino@apache.org>
Fri, 18 May 2018 14:50:52 +0000 (10:50 -0400)
gateway-server/src/main/java/org/apache/knox/gateway/GatewayMessages.java
gateway-server/src/main/java/org/apache/knox/gateway/services/topology/impl/DefaultTopologyService.java

index b4a0adb..743b958 100644 (file)
@@ -559,9 +559,7 @@ public interface GatewayMessages {
                                              @StackTrace( level = MessageLevel.DEBUG ) Exception e );
 
   @Message( level = MessageLevel.WARN, text = "An error occurred while attempting to start the remote configuration monitor {0} : {1}" )
-  void remoteConfigurationMonitorStartFailure(final String monitorType,
-                                              final String errorMessage,
-                                              @StackTrace( level = MessageLevel.DEBUG ) Exception e );
+  void remoteConfigurationMonitorStartFailure(final String monitorType, final String errorMessage);
 
   @Message( level = MessageLevel.INFO, text = "Starting remote configuration monitor for source {0} ..." )
   void startingRemoteConfigurationMonitor(final String address);
index ab5cedf..7482389 100644 (file)
@@ -540,7 +540,7 @@ public class DefaultTopologyService
       try {
         remoteMonitor.start();
       } catch (Exception e) {
-        log.remoteConfigurationMonitorStartFailure(remoteMonitor.getClass().getTypeName(), e.getLocalizedMessage(), e);
+        log.remoteConfigurationMonitorStartFailure(remoteMonitor.getClass().getTypeName(), e.getLocalizedMessage());
       }
     }
   }