Summary:	ASTERISK-27268: pjsip: Lockup PJSIP Invite+Reg Processing Taskprocessor w/ distributor backup
Reporter:	Joshua Elson (joshelson)	Labels:
Date Opened:	2017-09-13 17:57:08	Date Closed:	2017-09-13 19:24:36
Priority:	Major	Regression?
Status:	Closed/Complete	Components:
Versions:	14.6.1	Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) distributor-backtrace.txt ( 1) taskprocessors.txt
Description:	Daily issue seen with pjsip realtime and distributor lockup on a relatively lightly loaded box.
Comments:	By: Asterisk Team (asteriskteam) 2017-09-13 17:57:09.300-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 Elson (joshelson) 2017-09-13 17:57:50.549-0500 Attaching backtrace of locked system and partial list of taskprocessors indicating issue. By: Richard Mudgett (rmudgett) 2017-09-13 19:06:31.886-0500 Threads 73 and 74 appear to be deadlocked in bridge_p2p_rtp_write() trying to get the AST_RTP_PROPERTY_ASYMMETRIC_CODEC property of the bridged peer rtp instance.  AST_RTP_PROPERTY_ASYMMETRIC_CODEC doesn't exist on the reported 14.6.1 and the line numbers do not match inside res_rtp_asterisk.c. By: Joshua Elson (joshelson) 2017-09-13 19:20:25.737-0500 You are correct. Doh. Didn't realize we'd taken this patch. We applied this, it appears: https://gerrit.asterisk.org/#/c/6186/ Double checking to see if we're on the exact patch that was merged. By: Joshua Elson (joshelson) 2017-09-13 19:24:27.143-0500 This patch was updated because of this known deadlock issue. My apologies. We'll update on our end.