Summary:	ASTERISK-27958: Deadlock in res_pjsip_registrar on contact transport shutdown
Reporter:	Ross Beer (rossbeer)	Labels:	pjsip
Date Opened:	2018-07-10 06:03:43	Date Closed:	2018-07-23 07:00:54
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Resources/res_pjsip_registrar
Versions:	GIT	Frequency of Occurrence	Frequent
Related Issues:
Environment:	CentOS 7	Attachments:
Description:	A deadlock occurs on contact transport shutdown. Full backtraces have been sent over.
Comments:	By: Asterisk Team (asteriskteam) 2018-07-10 06:03:45.228-0500 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. 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]. By: Joshua C. Colp (jcolp) 2018-07-23 07:00:54.548-0500 After further investigation this does not appear to be a bug in Asterisk itself. Thread 80 shows Asterisk waiting on the MySQL ODBC client to respond after it is given a query to prepare to delete a contact. While this is happening the AOR itself is locked. The threads locking up are waiting to acquire the AOR lock. The MySQL ODBC client should return quickly, but it is not. Other threads are also seemingly blocked waiting for the database to respond throughout the backtrace.