1 Reply Latest reply on Oct 18, 2011 1:23 PM by Clebert Suconic

    Clogged Queue

    Arash Bijanzadeh Newbie

      I notice some strange behavior from the JMS queue on my 2.1.1 HornetQ. The definition of the Queues are :

       

            <address-setting match="#">

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

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

               <redelivery-delay>300000</redelivery-delay>

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

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

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

               <send-to-dla-on-no-route>true</send-to-dla-on-no-route>

               <max-delivery-attempts>60</max-delivery-attempts>

               <page-size-bytes>524268</page-size-bytes>

               <address-full-policy>PAGE</address-full-policy>

            </address-setting>

       

      After a few retry, HornetQ doesn't deliver my messages, and if it does, the delay is more than an hour. Another strange thing is the message count in the JMX console. The console reports a negative number for the number of messages in the queue.