8 Replies Latest reply on Sep 24, 2010 8:18 AM by Tim Fox

    15:43:18,247 WARN  [FilterImpl] Invalid filter string: JMSExpiration<1285249398244

    Veit Guna Newbie

      Hi.

       

      Before creating a new issue in JIRA I would like to make sure that this is really a bug and not my fault .

       

      We're migrating from JBoss 5.1.0 shipped JBoss Messaging 1.4.3 to HornetQ 2.1.2. After some

      struggling with MDB's not receiving messages anymore (BTW: a migration guide telling about the resource adaptor thing would be great)

      we get the folliowing exception:

       

      15:43:18,247 WARN  [FilterImpl] Invalid filter string: JMSExpiration<1285249398244
      java.lang.NullPointerException
          at org.hornetq.core.filter.impl.FilterImpl.match(FilterImpl.java:160)
          at org.hornetq.core.server.impl.ServerConsumerImpl.handle(ServerConsumerImpl.java:207)
          at org.hornetq.core.server.impl.QueueImpl.handle(QueueImpl.java:1384)
          at org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:1175)
          at org.hornetq.core.server.impl.QueueImpl.access$700(QueueImpl.java:67)
          at org.hornetq.core.server.impl.QueueImpl$DeliverRunner.run(QueueImpl.java:1601)
          at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100)
          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
          at java.lang.Thread.run(Thread.java:619)

       

      That worked before with JBM 1.4.3 without a problem. It's one of our components that's generating this selector string. Any ideas

      why that fails?