[
https://issues.apache.org/jira/browse/JAMES-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579653#comment-17579653
]
Adrian Bucher commented on JAMES-3803:
--------------------------------------
I checked your code and it works as well , i think it would be greate to
reintorduce deliveryThreads, but I still would keep the dequeueing thread on a
diffrent scheduler to reduce the risk errors due to the thread mix up, should I
reintroduce DeliveryThreads? or it this on your branch already done?
> 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
> Attachments: jstack-of-the-bug.txt
>
> Time Spent: 40m
> 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-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
