[asterisk-bugs] [JIRA] (ASTERISK-21389) res_timing_pthread fails to return from write, causing timer dependent operations to block indefinitely

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-21389:
-----------------------------------

    Target Release Version/s: 11.4.0
                              1.8.22.0
    
> res_timing_pthread fails to return from write, causing timer dependent operations to block indefinitely
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21389
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21389
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Resources/res_timing_pthread
>    Affects Versions: 1.8.20.0, 1.8.21.0
>            Reporter: Matt Jordan
>      Target Release: 1.8.22.0, 11.4.0
>
>         Attachments: 0001-res_timing_pthread-Reduce-probability-of-deadlocking.patch, backtrace1-threads.txt, backtrace-threads.txt
>
>
> Tony from Schmooze Com reported that since upgrading to Asterisk 1.8.20.x, there have been numerous apparent lock ups in {{chan_sip}}, wherein all calls stop being processed. Other operations (such as querying from the CLI) continue to work correctly.
> Two backtraces taken from affected systems point to a call to {{res_timing_pthread}}'s write_byte not returning. This call is attempting to write a byte into a timer's pipe. In general, while the pipe is blocking, this operation should write the byte and immediately return. Failure to return typically indicates that the pipe is full.
> It isn't clear right now which timer is actually causing the problem, nor is it clear why a read operation isn't being performed on some timer. However, as noted in ASTERISK-14050, having a single timer run into this state will cause this exact problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira