[asterisk-bugs] [JIRA] (ASTERISK-30313) threadpool: Control taskprocessor is blocked waiting for idle thread to terminate

[Mark Murawski (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260715#comment-260715 ] 

Mark Murawski commented on ASTERISK-30313:
------------------------------------------

Okay, so based on your update to the title, and the idle timeout setting (threadpool_idle_timeout).  

If one were to go about fixing this issue.  It sounds like there's one or more threads that are idle, but are not ending.  Are they really idle?  Maybe they were marked idle incorrectly and are still doing something?

Probably more logging needs to be added to resolve this?  There's only information regarding idle threads and destroying them. We don't have startups and pending waits.  It doesn't seem obvious which thread is being waited on that's blocking pjsip (maybe DEBUG_THREADS?)

I'll do some poking here.

> threadpool: Control taskprocessor is blocked waiting for idle thread to terminate
> ---------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30313
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30313
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: 18.14.0
>            Reporter: Mark Murawski
>            Assignee: Unassigned
>            Severity: Major
>         Attachments: core-asterisk-2022-11-19T15-12-39Z-brief.txt, core-asterisk-2022-11-19T15-12-39Z-full.txt, core-asterisk-2022-11-19T15-12-39Z-info.txt, core-asterisk-2022-11-19T15-12-39Z-locks.txt, core-asterisk-2022-11-19T15-12-39Z-thread1.txt, full-core-debug.log, pjsip.conf, pjsip_wizard.conf
>
>
> Unfortunately very random
> This can happen when there's:
> 0 calls
> 1 call
> 20 calls
> 100 calls
> I can't find a pattern to this yet.
> Attached core dumps



--
This message was sent by Atlassian JIRA
(v6.2#6252)