[asterisk-bugs] [JIRA] (ASTERISK-28516) Crash Under AMI Taskprocessor Backup

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-28516:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> Crash Under AMI Taskprocessor Backup
> ------------------------------------
>
>                 Key: ASTERISK-28516
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28516
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 16.4.0
>         Environment: CentOS 7
>            Reporter: Joshua Elson
>            Assignee: Joshua Elson
>         Attachments: brief.txt, full.txt, locks.txt, thread1.txt
>
>
> Seeing an interesting and possibly reproducible crash under a significant AMI taskprocessor backup. Crash path seems directly unrelated, but we can generate this condition with significant numbers of concurrent connection attempts to the AMI interface while the box is under "normal" other call load.



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