Re: growing #threads problem

I found the bug that let me to encounter this behaviour. I’ll keep an eye on this after I fixed it (simple stupid NPE). I don’t think it is a big problem as the DirectAgentCronJobs are maximised to 500 by default. Still strange that it keeps growing in a rather silent environment though. On

Re: growing #threads problem

Nproc == -1 , both soft and hard so unless this is inherited from VMs in nested environments this can’t be the problem Also no strange unexpected exceptions found, only failed connections to hosts during startup and environment configuration. On 11/04/17 12:01, "Koushik Das"

Re: growing #threads problem

Check the MS logs to see if there are OOM exceptions due to threads not available. If that’s the case then you may have to adjust nproc limits in /etc/security/limits.conf. On 11/04/17, 1:11 PM, "Daan Hoogland" wrote: My next step is to rebase my change to

Re: growing #threads problem

My next step is to rebase my change to 4.9 and see if that works. But that is a stab in the dark I must admit. On 11/04/17 09:30, "Daan Hoogland" wrote: Devs, While I am creating a runnable tob e scheduled I ran into a problem. My scheduledJob nevers

growing #threads problem

Devs, While I am creating a runnable tob e scheduled I ran into a problem. My scheduledJob nevers gets called and looking at the process the number of threads of type “DirectAgent-*” and “DirectAgentCronJob-*” keep growing. My job is scanning for templates in the primary storage and references