Memory usage limit can contriubte this issue. Since your queue's memory is exhausted by those messages that were dispatched to consumers but not acked by consumers. When broker page more messages from the store it will check if the queue has enough memory space to load new messages, if no then no more new messages will be loaded and dispatched to conumers.I suppose the memory usage limit of your queue is the default value(1MB),then when 1MB size messges have dispatched to your consumers and no acks come back, then broker can not dispatch more messages due to memory usage limit.
At 2013-08-01 22:36:34,"Christian Posta" <christian.po...@gmail.com> wrote: >Post your client code > >On Wednesday, July 31, 2013, Swapnil wrote: > >> Yes, I am calling commit on the session but only after receiving say X >> number >> of messages. Consumer will accumulate X number of messages before >> processing >> and acknowledging them. >> >> This X is configurable number. We tried with 500 and consumer was receiving >> only around 350 messages. Messages which are enqueued and pending was >> around >> 5000. >> >> Number of messages sent by JMS varies as per the size of message (larger >> the >> size, less number of messages received by consumer). After sending say 350 >> messages to consumer, JMS waits till acknowledgment before sending further >> batch of messages. >> >> >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/ActiveMQ-stops-sending-messages-to-Queue-Consumer-in-case-of-consumer-not-acknowledging-messages-tp4669923p4669969.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> > > >-- >*Christian Posta* >http://www.christianposta.com/blog >twitter: @christianposta
