| Summary: | ASTERISK-28350: manager: Stasis backed up due to locking | ||
| Reporter: | Joshua C. Colp (jcolp) | Labels: | |
| Date Opened: | 2019-03-26 06:38:42 | Date Closed: | 2019-03-27 17:44:41 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | 13.25.0 16.2.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When notifying a manager session that new events were available the same lock was used that was also held when doing things within the session (such as sending events out). If the manager session blocked for a period of time this would cause a back up of messages in Stasis and would also block any other sessions from receiving events.
| ||
| Comments: | By: Friendly Automation (friendly-automation) 2019-03-27 17:44:42.809-0500 Change 11180 merged by Friendly Automation: manager: Use separate lock for session event notification. [https://gerrit.asterisk.org/c/asterisk/+/11180|https://gerrit.asterisk.org/c/asterisk/+/11180] By: Friendly Automation (friendly-automation) 2019-03-28 08:05:26.501-0500 Change 11181 merged by George Joseph: manager: Use separate lock for session event notification. [https://gerrit.asterisk.org/c/asterisk/+/11181|https://gerrit.asterisk.org/c/asterisk/+/11181] By: Friendly Automation (friendly-automation) 2019-03-28 08:05:36.118-0500 Change 11179 merged by George Joseph: manager: Use separate lock for session event notification. [https://gerrit.asterisk.org/c/asterisk/+/11179|https://gerrit.asterisk.org/c/asterisk/+/11179] | ||