Re: Killing long-running tasks

Hello Jerry,

Which backend are you using? JPA ?

On 06/10/2022 08:32, Jerry Malcolm wrote:
> A client yesterday had a folder with 20,000 emails and decided to 
> delete and/or move most of them to other folders (using Thunderbird 
> client).  The server slowed to a crawl. Since that time, opening any 
> folder on any account takes forever with Thunderbird timing out most 
> of the time.  I've tried rebooting james several times.  No luck.  
> Does James cache long-running tasks and continue on the tasks after a 
> reboot?
No.
> If so, how do I kill the task(s) permanently?  If tasks do not carry 
> over across reboots, where is the best place to look in the logs to 
> see what has is causing the server to go to its knees?  It's been 36 
> hours and it's still barely responding.
I would recommend you starting an Application Performance Manager like 
glowroot. We have some set up on it to capture IMAP transactions, and it 
should support SQL queries as well, you would be able to investigate 
your slow traces. Link to a James set up with glowroot: 
https://github.com/apache/james-project/tree/master/server/apps/distributed-app/src/main/glowroot
>
> Thx
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>