[JAMES-3803] DeliveryRunnable blocks email in BoundedElasticScheduler-queue if running out of threads

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.7.0
• Fix Version/s: 3.8.0
• Component/s: Remote Delivery
• Assignee: Unassigned
• Reporter: Adrian Bucher
• Created: 11/Aug/22 09:28
• Updated: 19/Aug/22 09:19
• Resolved: 19/Aug/22 09:19

Description

The DeliveryRunnable does use the same BoundedElasticScheduler (ThreadPool) for dequeuing the messages (long running thread), and processing (delivering) them, if lots of messages are dequeued and the BoundedElasticScheduler starts to queue them, the one queueing behind the dequeuing - long running thread are never processed nor delivered.

 

Messages are still visible in the embedded activemq delivery queues, a restart of the james will process them, as they will be reacknoledged by the dequeuer.

 

 

Issue Links

• links to: GitHub Pull Request #1121