That helps. Is this a network of brokers? Are clients using transactions?
In addition to the diagnostics Gary mentioned, grabbing a stack trace when this happens may be helpful. Are JMSXGroups in-use? Also, are the producers using the failover transport, or using any other technology that might hold and resend messages after a broker restart? If you can reproduce this easily with a minimal test case, then I'll give it a try. > > > > Hi Artnaseef, > > Unconsumed messages are detected with the application which is time > sensitive is not updating. > > I am sure that there is data in the queue. When blocked for a period of > time > the enqueue will increase until the broker is restarted. The data payload > is > time stamped to I can tell that it is historic data when the application > processes the data after the reset. > > The ttl is not set on these message so it is default, which is unlimited. > Yes restarting the broker resumes progressing and previous unconsumed > messages are consumed. > > Not to sure what the jmx QueueSize is but it I can tell from the admin > console that the enqueue is increasing when stuck > > Thanks > lookers > > > > _______________________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-5-9-0-tp4679266p4679607.html > To start a new topic under ActiveMQ - User, email > [email protected] > To unsubscribe from ActiveMQ - User, visit > http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=2341805&code=YXJ0QGFydG5hc2VlZi5jb218MjM0MTgwNXwtMjA1NDcyNjY5MQ== -- View this message in context: http://activemq.2283324.n4.nabble.com/Messages-stuck-in-queue-5-9-0-tp4679266p4679612.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
