Better handling for exception logs

Handling for dmaap not supporting offsets

Issue-ID: AAI-552
Change-Id: I0af737d92861b7c6c22421a106d32c9b2c4fca7b
Signed-off-by: Gurjeet Bedi <gurjeetb@amdocs.com>

1 files changed, 8 insertions, 1 deletions

diff --git a/src/main/java/org/onap/crud/service/CrudAsyncResponseConsumer.java b/src/main/java/org/onap/crud/service/CrudAsyncResponseConsumer.java
index da7e6e5..905fe15 100644
--- a/src/main/java/org/onap/crud/service/CrudAsyncResponseConsumer.java
+++ b/src/main/java/org/onap/crud/service/CrudAsyncResponseConsumer.java
@@ -25,6 +25,8 @@ package org.onap.crud.service;
 
 import java.util.TimerTask;
 
+import javax.naming.OperationNotSupportedException;
+
 import org.onap.aai.cl.api.Logger;
 import org.onap.aai.cl.eelf.LoggerFactory;
 import org.onap.crud.event.GraphEvent;
@@ -107,7 +109,12 @@ public class CrudAsyncResponseConsumer extends TimerTask {
 
     try {
       asyncResponseConsumer.commitOffsets();
-    } catch (Exception e) {
+    }
+    catch(OperationNotSupportedException e) {
+        //Dmaap doesnt support commit with offset    
+        logger.debug(CrudServiceMsgs.ASYNC_RESPONSE_CONSUMER_ERROR, e.getMessage());
+    }
+    catch (Exception e) {
       logger.error(CrudServiceMsgs.ASYNC_RESPONSE_CONSUMER_ERROR, e.getMessage());
     }