[asterisk-bugs] [JIRA] Commented: (ASTERISK-20347) Asterisk 1.8.16rc1 deadlock in cdr_mysql

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-20347:
----------------------------------------

No, {{cdr_odbc}} is extended support as well.  The core supported CDR modules in Asterisk 1.8 are:

* {{cdr_adaptive_odbc}}
* {{cdr_custom}}
* {{cdr_manager}}
* {{cdr_syslog}}

You can get a listing of the support status for each module in the {{menuselect}} tool.

> Asterisk 1.8.16rc1 deadlock in cdr_mysql
> ----------------------------------------
>
>                 Key: ASTERISK-20347
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20347
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/cdr_mysql
>    Affects Versions: 1.8.16.0
>         Environment: Centos 5.8 x64, 8core, 8GB RAM
>            Reporter: aragon
>            Severity: Critical
>         Attachments: coreshowlocks.txt, thread-apply-all-bt.txt
>
>
> As per Matt Jordan I am opening a bug report for a deadlock found in Asterisk 1.8.16rc and cdr_mysql.
> All I have for now is a gdb backtrace unoptimized but should soon be able to provide a non-optimized bt and core show locks output.  Opening ticket without that for now...

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira