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

["Benoit Tellier (Jira)" <se...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/JAMES-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Tellier closed JAMES-3803.
---------------------------------
    Fix Version/s: 3.8.0
       Resolution: Fixed

I merged the fix on master.

Don't hesitate to backport it on 3.7.x branch ;-)

> DeliveryRunnable blocks email in BoundedElasticScheduler-queue if running out of threads
> ----------------------------------------------------------------------------------------
>
>                 Key: JAMES-3803
>                 URL: https://issues.apache.org/jira/browse/JAMES-3803
>             Project: James Server
>          Issue Type: Bug
>          Components: Remote Delivery
>    Affects Versions: 3.7.0
>            Reporter: Adrian Bucher
>            Priority: Major
>             Fix For: 3.8.0
>
>         Attachments: jstack-of-the-bug.txt
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> 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.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org