[asterisk-bugs] [JIRA] (ASTERISK-27385) channel.c: Exceptionally long queue length queuing

[Abhay Gupta (JIRA)]

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

Abhay Gupta commented on ASTERISK-27385:
----------------------------------------

The steps that i used to reproduce this issue was resolved when Asterisk was updated to 13.18.2 but still this problem comes which i am unable to reproduce . Only thing that i could see was some locks that were resolved in 13.18.2 related to media on registration and so i suppose something similar is a issue pending in some other portion .

If you can help let me know any code that i can put in certain functions in source which could help trace the issue i can do so but i am not able to enable core show locks as the server is heavily loaded 

> channel.c: Exceptionally long queue length queuing
> --------------------------------------------------
>
>                 Key: ASTERISK-27385
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27385
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging
>    Affects Versions: 13.17.2
>         Environment: Ubuntu 16.04 with asterisk 13.17.2 using Staisis 
>            Reporter: Abhay Gupta
>            Assignee: Abhay Gupta
>         Attachments: abhay.txt, asterisk logs.txt, asterisk_top.png, core-asterisk-running-2017-11-08T12-30-19+0530-brief.txt, core-asterisk-running-2017-11-08T12-30-19+0530-full.txt, core-asterisk-running-2017-11-08T12-30-19+0530-locks.txt, core-asterisk-running-2017-11-08T12-30-19+0530-thread1.txt, full, gdb.txt, pjsip_settings.txt, server_info.txt, stasis.conf, stucked_call.txt, task_noproblem.txt, taskprocessors
>
>
> Asterisk becomes unstable with message like 
> [Oct 31 10:37:37] WARNING[5608][C-00001b6b] channel.c: Exceptionally long queue length queuing to Local/2048 at sxxxxxxg-000016ba;1
> There are two staisis customer-dial and agent-dial . The steps seems to be as follows 
> 1. A Sip channel is added in customer-dial 
> 2. A manager originate command adds a channel between customer-dial and agent-dial while the existing channel is hanging up in customer-dial 
> 3. Both channels of customer-dial are bridged while some clearing is happening on the channel which is getting hangup / deleted .
> This problem appears 



--
This message was sent by Atlassian JIRA
(v6.2#6252)