Server Side Filters: JMSTimestamp must be 0 long when it is not set (#55

)
datastax · Aug 22, 2022 · 85ffcc0 · 85ffcc0
1 parent b57b79b
commit 85ffcc0
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/pulsar-jms-filters/src/main/java/com/datastax/oss/pulsar/jms/selectors/JMSFilter.java b/pulsar-jms-filters/src/main/java/com/datastax/oss/pulsar/jms/selectors/JMSFilter.java
@@ -283,7 +283,9 @@ public FilterResult filterEntry(Entry entry, FilterContext context) {
       }
 
     } catch (Throwable err) {
-      log.error("Error while decoding batch entry", err);
+      log.error("Error while processing entry " + err, err);
+      // also print on stdout:
+      err.printStackTrace(System.out);
       return FilterResult.REJECT;
     }
   }
@@ -374,7 +376,7 @@ public Object apply(String name) {
                 return metadata.getEventTime();
               }
             }
-            return 0;
+            return 0L; // must be a long
           }
         case "JMSXDeliveryCount":
           // this is not supported on the broker