Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7115

Large Messages are stuck if sent through Clustered bridge

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • EAP_EWP 5.1.2 ER1
    • EAP_EWP 5.1.1
    • HornetQ
    • None

    • JBoss-EAP-5.1, HornetQ-2.2.4
      JBoss-EAP-5.1.1 HornetQ-2.2.5-GA

    • Hide
      • Configure two HornetQ clusters using the attached configuration files
      • Send more than 2 messages to the master node. The first node in the cluster
      • You could see messages getting stuck at the cluster generated
        "sf.my-cluster" queue and it throws the following error :

      18:42:48,889 WARN [QueueImpl] removing consumer which did not handle a message, consumer=org.hornetq.core.server.cluster.impl.ClusterConnectionBridge@4777eb45, message=Reference[28]:RELIABLE:ServerMessage[messageID=28,priority=4,expiration=[null], durable=true, address=jms.queue.A,properties=TypedProperties[{_HQ_LARGE_SIZE=2097157, _HQ_ROUTE_TOsf.my-cluster.71f94b8c-d475-11e0-bdb6-a088b40ff618=[B@e888e0}]]
      java.lang.NullPointerException
      at org.hornetq.core.buffers.impl.ResetLimitWrappedHornetQBuffer.<init>(ResetLimitWrappedHornetQBuffer.java:39)
      at org.hornetq.core.message.impl.MessageImpl.getBodyBuffer(MessageImpl.java:267)
      at org.hornetq.core.client.impl.ClientProducerImpl.doSend(ClientProducerImpl.java:223)
      at org.hornetq.core.client.impl.ClientProducerImpl.send(ClientProducerImpl.java:142)
      at org.hornetq.core.server.cluster.impl.BridgeImpl.handle(BridgeImpl.java:407)
      at org.hornetq.core.server.impl.QueueImpl.handle(QueueImpl.java:2017)
      at org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:1587)
      at org.hornetq.core.server.impl.QueueImpl.doPoll(QueueImpl.java:1472)
      at org.hornetq.core.server.impl.QueueImpl.access$1100(QueueImpl.java:72)
      at org.hornetq.core.server.impl.QueueImpl$ConcurrentPoller.run(QueueImpl.java:2299)
      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:662)
      18:42:48,890 ERROR [OrderedExecutorFactory] Caught unexpected Throwable
      java.util.NoSuchElementException
      at org.hornetq.utils.PriorityLinkedListImpl$PriorityLinkedListIterator.repeat(PriorityLinkedListImpl.java:189)
      at org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:1604)
      at org.hornetq.core.server.impl.QueueImpl.doPoll(QueueImpl.java:1472)
      at org.hornetq.core.server.impl.QueueImpl.access$1100(QueueImpl.java:72)
      at org.hornetq.core.server.impl.QueueImpl$ConcurrentPoller.run(QueueImpl.java:2299)
      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:662)

      Show
      Configure two HornetQ clusters using the attached configuration files Send more than 2 messages to the master node. The first node in the cluster You could see messages getting stuck at the cluster generated "sf.my-cluster" queue and it throws the following error : 18:42:48,889 WARN [QueueImpl] removing consumer which did not handle a message, consumer=org.hornetq.core.server.cluster.impl.ClusterConnectionBridge@4777eb45, message=Reference [28] :RELIABLE:ServerMessage[messageID=28,priority=4,expiration= [null] , durable=true, address=jms.queue.A,properties=TypedProperties[{_HQ_LARGE_SIZE=2097157, _HQ_ROUTE_TOsf.my-cluster.71f94b8c-d475-11e0-bdb6-a088b40ff618= [B@e888e0}] ] java.lang.NullPointerException at org.hornetq.core.buffers.impl.ResetLimitWrappedHornetQBuffer.<init>(ResetLimitWrappedHornetQBuffer.java:39) at org.hornetq.core.message.impl.MessageImpl.getBodyBuffer(MessageImpl.java:267) at org.hornetq.core.client.impl.ClientProducerImpl.doSend(ClientProducerImpl.java:223) at org.hornetq.core.client.impl.ClientProducerImpl.send(ClientProducerImpl.java:142) at org.hornetq.core.server.cluster.impl.BridgeImpl.handle(BridgeImpl.java:407) at org.hornetq.core.server.impl.QueueImpl.handle(QueueImpl.java:2017) at org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:1587) at org.hornetq.core.server.impl.QueueImpl.doPoll(QueueImpl.java:1472) at org.hornetq.core.server.impl.QueueImpl.access$1100(QueueImpl.java:72) at org.hornetq.core.server.impl.QueueImpl$ConcurrentPoller.run(QueueImpl.java:2299) 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:662) 18:42:48,890 ERROR [OrderedExecutorFactory] Caught unexpected Throwable java.util.NoSuchElementException at org.hornetq.utils.PriorityLinkedListImpl$PriorityLinkedListIterator.repeat(PriorityLinkedListImpl.java:189) at org.hornetq.core.server.impl.QueueImpl.deliver(QueueImpl.java:1604) at org.hornetq.core.server.impl.QueueImpl.doPoll(QueueImpl.java:1472) at org.hornetq.core.server.impl.QueueImpl.access$1100(QueueImpl.java:72) at org.hornetq.core.server.impl.QueueImpl$ConcurrentPoller.run(QueueImpl.java:2299) 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:662)
    • Compatibility/Configuration
    • In a clustered HornetQ configuration, messages 1 MB or larger in size could get stuck in the queue, resulting in a NullPointerException. This has been solved with large messages now catered for in a clustered configuration.
    • Documented as Resolved Issue
    • NEW

      Large text messages of the size of 1MB get stuck in "sf.my-cluster".

        1. hq-test.zip
          3 kB

              csuconic@redhat.com Clebert Suconic
              rhn-support-tywickra Tyronne Wickramarathne
              Russell Dickenson Russell Dickenson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: