I noticed you use message groups. What does your consumer logic do? Is it possible that some messages take longer to process?
Do you have a finite set of message groups? How do you start your consumers? Do you start them when the queue already contains messages? Are consumers fixed? Or do they come and go? Have you checked the JMX stats for consumers? Are they all processing messages? I think this may be a problem with message group partitioning. Raúl. On 20 Aug 2015 16:42, "Richard Sinek" <rsi...@intouchgps.com> wrote: > I have an issue where my consumer stops receiving messages for 10 or 15 > minutes, then resumes. This is load dependent - the faster the message rate > the more frequently it occurs. We have assumed that it is an issue at the > consumer level but have not been able to pin down the cause. > > However, sometimes I suspect AMQ as if I have 2 separate applications > consuming - running on 2 separate virtual servers the message flow stops > simultaneously on both. > > Using kahadb for store. > Persistent messaging > Message rates are low - only 10's to low 100's per sec across multiple > queues > We use message_groups and multiple consumers (4-8) per application instance > > I have not found any configuration or setting in the documentation that > might explain this at the AMQ server level. I am hoping someone out there > has some similar experience and could possibly shed some light. > > We have AMQ running versions 5.9.1 and 5.11.1 and the issue has been > observed on all. > > Richard > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/AMQ-pauses-sending-to-consumers-tp4701242.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
