0 Replies Latest reply on Jul 13, 2012 5:06 AM by Simone Saba

    paging blocks message delivery

    Simone Saba Newbie

      on JBoss 6.1 GA, clustered conf but working on a single node,

      I'm using PAGE policy on address full for persistent messages,

      as far as we're enqueuing everything is ok the page files are created

      and the queue grows, but when the messages are consumed to the

      point they should be extracted from the paging files the consuming stops

      on reboot I get the following exceptions:

       

      16:46:29,276 WARN  [QueueImpl] removing consumer which did not handle a message, consumer=org.hornetq.core.server.impl.ServerConsumerImpl@55cfffa2

      , message=PagedReferenceImpl [position=PagePositionImpl [pageNr=1, messageNr=9, recordID=0], message=PagedMessageImpl [queueIDs=[73], transactionI

      D=55948, message=ServerMessage[messageID=55947,priority=4,expiration=0, durable=true, address=MYQUEUE.address,properties

      =TypedProperties[{_HQ_DUPL_ID=62799|497|RETRY|2, parentTransactionId=8615d62a-57c4-4d8e-a01d-3178e6d33d82}]]], deliveryTime=0, persistedCount=1, d

      eliveryCount=1, subscription=PageSubscriptionImpl [cursorId=73, queue=QueueImpl[name=MYQUEUE]@41c7d5a8]]: java.lang.IllegalStateException: Cannot find add info 55947

              at org.hornetq.core.journal.impl.JournalImpl.appendUpdateRecord(JournalImpl.java:910) [:6.1.0.Final]

              at org.hornetq.core.persistence.impl.journal.JournalStorageManager.updateDeliveryCount(JournalStorageManager.java:760) [:6.1.0.Final]

              at org.hornetq.core.server.impl.ServerConsumerImpl.handle(ServerConsumerImpl.java:267) [:6.1.0.Final]

              at org.hornetq.core.server.impl.QueueImpl.handle(QueueImpl.java:2017) [:6.1.0.Final]

              at org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:1587) [:6.1.0.Final]

              at org.hornetq.core.server.impl.QueueImpl.doPoll(QueueImpl.java:1472) [:6.1.0.Final]

              at org.hornetq.core.server.impl.QueueImpl.access$1100(QueueImpl.java:72) [:6.1.0.Final]

              at org.hornetq.core.server.impl.QueueImpl$ConcurrentPoller.run(QueueImpl.java:2299) [:6.1.0.Final]

              at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.1.0.Final]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_24]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_24]

              at java.lang.Thread.run(Thread.java:679) [:1.6.0_24]

       

      16:46:29,280 ERROR [OrderedExecutorFactory] Caught unexpected Throwable: java.util.NoSuchElementException

              at org.hornetq.utils.PriorityLinkedListImpl$PriorityLinkedListIterator.repeat(PriorityLinkedListImpl.java:189) [:6.1.0.Final]

              at org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:1604) [:6.1.0.Final]

              at org.hornetq.core.server.impl.QueueImpl.doPoll(QueueImpl.java:1472) [:6.1.0.Final]

              at org.hornetq.core.server.impl.QueueImpl.access$1100(QueueImpl.java:72) [:6.1.0.Final]

              at org.hornetq.core.server.impl.QueueImpl$ConcurrentPoller.run(QueueImpl.java:2299) [:6.1.0.Final]

              at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [:6.1.0.Final]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_24]

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_24]

              at java.lang.Thread.run(Thread.java:679) [:1.6.0_24]

       

      afterwards there's no way to restart message consumption, after a few reboots some message get in the DLQ but that's all I can get

       

      consumer code should be fine because without paging everything is working reliably

       

      looks like a hornetq bug to me but all similar errors I can find on the site a reported fixed (this is not, tried with hornetq 2.2.14 with the same result)

       

      should I open a bug?