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

1 files changed, 2 insertions, 1 deletions

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 08978699..087883dd 100755
--- 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;
 

 import javax.annotation.Resource;

 

+import com.google.common.base.Throwables;

 import org.onap.usecaseui.server.bean.AlarmsHeader;

 import org.onap.usecaseui.server.bean.AlarmsInformation;

 import org.onap.usecaseui.server.bean.SortMaster;

@@ -192,7 +193,7 @@ public class AlarmController
             return getDiagram(sourceName, startTimel, endTimel + timeInterval, timeInterval, 1, 1, format);

         } catch (Exception e) {

             logger.error("alarmController diagram occured exception:" + e.getMessage());

-            e.printStackTrace();

+            logger.error("alarmController diagram occured exception:"+ Throwables.getStackTraceAsString(e));

         }

         return null;

     }