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

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29465:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> 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
>
> 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)