[asterisk-bugs] [JIRA] (ASTERISK-29465) PJSIP/Outreg taskprocessor overload during simple outage

[Joshua C. Colp (JIRA)]

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

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

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

> PJSIP/Outreg taskprocessor overload during simple outage
> --------------------------------------------------------
>
>                 Key: ASTERISK-29465
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29465
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 16.18.0
>         Environment: CentOS 7 x64
>            Reporter: Luke Escude
>            Assignee: Luke Escude
>
> I am not certain if this is to be considered an issue, but it does appear to be a behavioral oddity.
> We have Asterisk registering outbound to our SIP Proxy servers at various edge locations via TCP (we don't use UDP).
> If a particular edge proxy goes down, naturally Asterisk realizes this, and the devices that were registering through that proxy are marked down, etc.
> However, Asterisk begins throwing up a bunch of these warnings:
> [Jun  4 14:46:15] WARNING[70]: taskprocessor.c:1160 taskprocessor_push: The 'pjsip/outreg/proxy-newyork-000000e6' task processor queue reached 500 scheduled tasks.
> [Jun  4 14:46:15] WARNING[70]: taskprocessor.c:1160 taskprocessor_push: The 'pjsip/outreg/proxy-newyork-000000e6' task processor queue reached 500 scheduled tasks again.
> [Jun  4 14:46:15] WARNING[70]: taskprocessor.c:1160 taskprocessor_push: The 'pjsip/outreg/proxy-newyork-000000e6' task processor queue reached 500 scheduled tasks again.
> [Jun  4 14:46:15] WARNING[70]: taskprocessor.c:1160 taskprocessor_push: The 'pjsip/outreg/proxy-newyork-000000e6' task processor queue reached 500 scheduled tasks again.
> I think I can re-create the issue as much as you guys want, by simulating outages, if you think this merits further exploration.



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