Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9639

Messages are stuck in a Queue that is configured on HornetQ

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 9.x.x TBD
    • JMS
    • None
    • Hide

      This issues is difficult to reproduce since it doesn't happen all the times. Happens at random.

      Stpes reproduce:
      1) Configure HornetQ server
      2) Configure ConnectionFactory and Queues (2 of them)
      3) Publish 1000 messages to the first Queue
      4) Deploy a number of Consumers (high concurrency) that implement MessageListener interface and deploy them into WildFly using Springs DefaultMessageListener
      5) All the 1000 messages will not be delivered to the consumers

      Show
      This issues is difficult to reproduce since it doesn't happen all the times. Happens at random. Stpes reproduce: 1) Configure HornetQ server 2) Configure ConnectionFactory and Queues (2 of them) 3) Publish 1000 messages to the first Queue 4) Deploy a number of Consumers (high concurrency) that implement MessageListener interface and deploy them into WildFly using Springs DefaultMessageListener 5) All the 1000 messages will not be delivered to the consumers

    Description

      We use WildFly 9.0.2 for hosting our web application and it has both real time and batch processing components. One of the functions supported on the web includes uploading a file with a number of lines any where from 1 to 10K, If the file is valid (virus scan etc passed) it is parsed into that may messages and published to a queue. Each message will have two counters total number of messages that are published to the queue, and the message number.
      The consuming side is implemented using Spring DefaultMessageListenerContainer (DMLC) with a concurrency of 50 and maxConcurrency of 75. The listeners that implement MessageListener interface are integrated into DMLC. sometimes, if the producing side published 100 messages the consuming side only receiving 98 (per say) and gets stuck because two more messages should be in the Queue. Those two messages are not delivered and don't know where they are going. We tried even persistent Queues and the result is same (getting stuck).
      This is happening in production and any insight into this issue is highly appreciated.

      Here are the software details:
      App server : Wildfly 9.0.2
      HornetQ : 2.4.7
      JDK : 1_8_144

      If you need additional details I will be very glad to provide.

      Thanks
      Rajendra

      Attachments

        Activity

          People

            jmesnil1@redhat.com Jeff Mesnil
            rmallamp_jira Rajendra Mallampati (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: