Summary:	ASTERISK-20757: Deadlock with 1.8 certified when abandoning queue calls
Reporter:	Marc Soda (msoda)	Labels:
Date Opened:	2012-11-30 10:27:57.000-0600	Date Closed:	2012-11-30 15:41:07.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:
Versions:	1.8.11.1	Frequency of Occurrence	Constant
Related Issues:
Environment:		Attachments:	( 0) core_show_locks.txt ( 1) core.deadlock.gz
Description:	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.
Comments:	By: Paul Belanger (pabelanger) 2012-11-30 15:40:51.248-0600 You'll have to open a support ticket with Digium for certified asterisk. Please see the following: http://www1.digium.com/en/products/asterisk/certified-asterisk By: Leif Madsen (lmadsen) 2012-12-01 14:27:25.034-0600 [~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. By: Leif Madsen (lmadsen) 2012-12-01 14:30:39.332-0600 Reduced to major since blocker should only be set for blocking a release. By: Paul Belanger (pabelanger) 2012-12-01 14:35:30.046-0600 Right, I should have been more descriptive. We cannot support certified asterisk on the open source tracker, reproduce the issue with the latest open source release otherwise obtain an SLA from Digium. I think we need a new canned response. By: Kevin McAllister (mcallist) 2012-12-03 14:05:50.280-0600 You may all be happy to know that this issue seems to be addressed in the certified source released today. Though the fact that a merge issue eliminating an unlock call gets released under something called "certified" is a little disconcerting.