Yes. I agree generally but I was worried about SOME other bug with the high DLQ message count. But if these two are coordinated then I only have to deal with the GC purgatory issue.
On Sun, Jan 4, 2015 at 6:59 PM, artnaseef <a...@artnaseef.com> wrote: > If the broker is getting into GC purgatory, as you describe, I wouldn't > bother trying to figure out why its operation is sub-optimal - that's > normal > for any java application in GC purgatory. > > Look for a memory leak or other errant operation that would explain the > constant GC activity. > > The results described - messages ending up in a DLQ - sounds like message > TTLs are expiring because the broker is far too slow delivering the > messages. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/high-GC-activity-yields-a-high-percentage-of-dead-letter-queue-messages-tp4689344p4689415.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
