[asterisk-bugs] [JIRA] (ASTERISK-30447) Stasis/p:channel:all reaching 500 tasks

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp updated ASTERISK-30447:
--------------------------------------

    Assignee: Luke Escude
      Status: Waiting for Feedback  (was: Triage)

Asterisk 16 no longer receives bug fixes.

As for that topic, it is a topic for all events for all channels. The more channels, the more events. Depending on usage it can be subscribed to by AMI, so if an AMI consumer is slow that may have an impact.

16 may have stasis statistics if you enable developer mode, they show up under the "stasis statistics" CLI commands which can narrow down what is backed up in stasis. As I originally stated though no changes would be done to Asterisk 16.

> Stasis/p:channel:all reaching 500 tasks
> ---------------------------------------
>
>                 Key: ASTERISK-30447
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30447
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_stasis
>    Affects Versions: 16.30.0
>            Reporter: Luke Escude
>            Assignee: Luke Escude
>
> Starting last week, some of our larger Asterisk instaces are logging a bunch of these:
> The 'stasis/p:channel:all-0000513d' task processor queue reached 500 scheduled tasks.
> I haven't found much about the p:channel:all task processor (there's some documentation around the others, but not this one).



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