0 Replies Latest reply on Jul 17, 2017 6:14 AM by versatile62

    HornetQ Lost Messages and Configurations

    versatile62 Newbie

      HornetQ Message are lost

      Hi,

      We are using HonertQ with Jboss 7 in cluster and non-clustered mode with following default configurations.

       

      <journal-file-size>102400</journal-file-size>

      <journal-min-files>2</journal-min-files>

       

      <address-settings>

          <address-setting match="#">

            <dead-letter-address>jms.queue.DLQ</dead-letter-address>

            <expiry-address>jms.queue.ExpiryQueue</expiry-address>

            <redelivery-delay>0</redelivery-delay>

            <max-size-bytes>10485760</max-size-bytes>

            <address-full-policy>BLOCK</address-full-policy>

            <message-counter-history-day-limit>10</message-counter-history-day-limit>

            <redistribution-delay>1000</redistribution-delay>

          </address-setting>

      </address-settings>

       

      In clustered mode there are around 350+ users and in non-clustered mode 50 users. Thousands of the messages are sent to queue at once, but sometimes in both environments few messages are not getting consumed, they are lost and orders/requests do not get processed. Later on resending/reposting all the lost message are processed successfully.

      What could be the possible reason of message loss and what are the ideal configurations for following and do we need to make any changes in above configurations as well or should we use paging as address-full-policy?

       

      Configuring the Expiry Reaper Thread

      Dead Letter Addresses

      Delayed Redelivery