You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Adrian Bucher (Jira)" <se...@james.apache.org> on 2022/08/11 09:32:00 UTC
[jira] [Updated] (JAMES-3803) DeliveryRunnable blocks email in BoundedElasticScheduler-queue if running out of threads
[ https://issues.apache.org/jira/browse/JAMES-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Bucher updated JAMES-3803:
---------------------------------
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.
was: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.
> 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: Mailet Contributions
> Affects Versions: 3.7.0, 3.8.0
> Reporter: Adrian Bucher
> Priority: Major
>
> 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