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.
