[
https://issues.apache.org/jira/browse/JAMES-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578419#comment-17578419
]
Adrian Bucher commented on JAMES-3803:
--------------------------------------
It is hard to reproduce,.. easiest way to reproduce it for sure is: set a
thread-suspending breakpoint in:
org.apache.james.transport.mailets.remote.delivery.DeliveryRunnable.processMail:120
(or anywhere else inside the Mono.
Then make it process alot of mails (No of CPU * 10) * 2, and wait untill they
all dequeued.
When you debug into the boundedElasticScheduler (line 94/96) you can see how
they get queued inside the reactiveStream, and as it has a queue for each
thread, one of this queues will not be processed.
We had this issues in our test when running with 1MB email sending it to slow
MTA, so the mails got faster dequeued from activemq then delivered. (queue size
must be higher then cpu * 10 as this is the default pool size )
> 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, 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-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
