[asterisk-bugs] [JIRA] (ASTERISK-20757) Deadlock with 1.8 certified when abandoning queue calls

[Leif Madsen (JIRA)]

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

Leif Madsen commented on ASTERISK-20757:
----------------------------------------

[~pabelanger] I think you can only open a ticket with Digium if you have support for CA directly. Otherwise, you likely need to reproduce with latest standard release (or from the 1.8 branch ideally) and then provide the output here for that version.
                
> Deadlock with 1.8 certified when abandoning queue calls
> -------------------------------------------------------
>
>                 Key: ASTERISK-20757
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20757
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.11.1
>            Reporter: Marc Soda
>            Severity: Blocker
>         Attachments: core.deadlock.gz, core_show_locks.txt
>
>
> We are experiencing an easily reproducible deadlock in Asterisk 1.8.11-cert8.  We have a queue setup with a rrmemory and two agents.  The system is under no load.
> Steps to reproduce:
> 1. Call into queue.
> 2. Agent 1 rings and rejects call.
> 3. Agent 2 rings and rejects call.
> 4. Agent 1 rings and rejects call.
> 5. Agent 2 rings and rejects call.
> 6. Caller hangs up.
> Asterisk is now in a deadlocked state.  Running 'core show locks' or 'queue show' produces no results.
> Note, that if you hang up after step 3 above a lock is still held and shows up in 'core show locks'.
> I will post the output of 'core show locks' and the core as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira