[asterisk-bugs] [JIRA] (ASTERISK-28605) Deadlock in Hangup Scenarios with concurrent command pri show span X

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp commented on ASTERISK-28605:
-------------------------------------------

We suspect that you have a deadlock occurring within Asterisk. Please follow the instructions on the wiki [1] for obtaining debug relevant to a deadlock. Once you have that information, attach it to the issue. Be sure the instructions are followed exactly as the debug may otherwise not be useful.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock



> Deadlock in Hangup Scenarios with concurrent command pri show span X
> --------------------------------------------------------------------
>
>                 Key: ASTERISK-28605
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28605
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/General
>    Affects Versions: 16.6.0
>         Environment: Asterisk 16.6 CentOs 6
>            Reporter: Dirk Wendland
>
> We have a Szenario with an high Call Flow ( load tests ).
> Szenario:
> 4 S2M Ports => 60 channels go up in the same second 60 Channels hangs up in the same second
> Every few seconds we check the ISN Lines with the command:
> pri show span X
> After a few iterations asterisk will stop working.
> On the console we can fire up that command only one time then that command line interface hangs.
> localhost*CLI> pri show span 4
> Primary D-channel: 109
> Status: Up, Active
> The next ( Switchtype ) will not be printed
> -----------------------------
> We found the patch/task that created that issue.
> https://issues.asterisk.org/jira/browse/ASTERISK-28525
> If we revert that commit everything works fine.
> Greetings
> Dirk



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