Usecaseui server sonar critical issue fix.

Usecase ui code was not having logger to capture the exception trace. The same is fixed.

Issue-ID: USECASEUI-304

Signed-off-by: Isaac Manuel Raj <isaac.manuelraj@huawei.com>
Change-Id: I0e42dd989f26835c1868b8a07ee63fb237cf5763

diff --git a/server/src/main/java/org/onap/usecaseui/server/controller/AlarmController.java b/server/src/main/java/org/onap/usecaseui/server/controller/AlarmController.java
index 0897869..087883d 100755 (executable)
--- a/server/src/main/java/org/onap/usecaseui/server/controller/AlarmController.java
+++ b/server/src/main/java/org/onap/usecaseui/server/controller/AlarmController.java
@@ -27,6 +27,7 @@ import java.util.Set;
 \r
 import javax.annotation.Resource;\r
 \r
+import com.google.common.base.Throwables;\r
 import org.onap.usecaseui.server.bean.AlarmsHeader;\r
 import org.onap.usecaseui.server.bean.AlarmsInformation;\r
 import org.onap.usecaseui.server.bean.SortMaster;\r
@@ -192,7 +193,7 @@ public class AlarmController
             return getDiagram(sourceName, startTimel, endTimel + timeInterval, timeInterval, 1, 1, format);\r
         } catch (Exception e) {\r
             logger.error("alarmController diagram occured exception:" + e.getMessage());\r
-            e.printStackTrace();\r
+            logger.error("alarmController diagram occured exception:"+ Throwables.getStackTraceAsString(e));\r
         }\r
         return null;\r
     }\r