[asterisk-bugs] [JIRA] (ASTERISK-28937) Task processor queue reached 500 scheduled tasks

[George Joseph (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Joseph updated ASTERISK-28937:
-------------------------------------

    Assignee: Shubham Agarwal
      Status: Waiting for Feedback  (was: Triage)

First, 15.5.0 is two years old and not longer supported.  I'd suggest upgrading to the latest version of Asterisk 16.  Having said that, there are generally 2 reasons for pjsip taskprocessor backups...  Slow DNS queries and slow database queries.

* When did this issue start happening?
* What changed between being stable and the issue happening?
* Local or remote database server?
* If remote, ping times between the Asterisk server and the database server.
* Database software and version.
* If using ODBC, ODBC version.

To get a better understanding of what's going on, follow the instructions linked below to get a backtrace of the running Asterisk instance at the time the issue is happening.  This will give us a better idea of a root cause.

https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


> Task processor queue reached 500 scheduled tasks
> ------------------------------------------------
>
>                 Key: ASTERISK-28937
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28937
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 15.5.0
>         Environment: Centos7
>            Reporter: Shubham Agarwal
>            Assignee: Shubham Agarwal
>            Severity: Minor
>
> We are using realtime PJSIP. We are noticing task processor warning after which Asterisk disconnects to all the endpoints and stop accepting any new request. 
> We are using Asterisk 15.5 and Centos 7. 
> taskprocessor.c: The ‘pjsip/distributor-00000167’ task processor queue reached 500 scheduled tasks.
> We are facing this issue very frequently. Please help us to get out of this. 



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