[asterisk-bugs] [JIRA] (ASTERISK-19754) Deadlock in chan_sip / pthread_timing

[Kien Kennedy (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198706#comment-198706 ] 

Kien Kennedy edited comment on ASTERISK-19754 at 10/18/12 2:57 AM:
-------------------------------------------------------------------

I had same problem, too. I have tried many version of asterisk (1.8.11, 1.8.15 and the newest 1.8.18-rc1) but the problem is still occured. The system was worked well in 1-2 months, but recently, it has these problems.
                
      was (Author: kiennd):
    I had same problem, too. I have tried many version of asterisk (1.8.11, 1.8.15 and the newest 1.8.18-rc1) but the problem is still occured.
                  
> Deadlock in chan_sip / pthread_timing
> -------------------------------------
>
>                 Key: ASTERISK-19754
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19754
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Resources/res_timing_pthread
>    Affects Versions: 1.8.11.0, 1.8.17.0, 1.8.18.0
>         Environment: Linux (centos 5), x86_64, kernel 3.0.x
>            Reporter: Nikola Ciprich
>            Severity: Critical
>         Attachments: ASTERISK-19754-core-show-locks.txt, backtrace-threads_1310.txt, core-show-locks_1310.txt
>
>
> from time to time, asterisk SIP handling seems to get into unresponsive state (no replies to INVITE, REGISTER etc).
> the culprit seems to be deadlock in chan_sip:
> [edit - mcj]
> core show locks output removed and put into attachment.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira