[asterisk-bugs] [JIRA] (ASTERISK-20718) Queues on virtual machines

[Dmitry Pavlenko (JIRA)]

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

Dmitry Pavlenko updated ASTERISK-20718:
---------------------------------------

    Attachment: backtrace-threads.rar

I used DONT OPTIMIZE, DEBUG THREADS and BETTER BACKTRACES compiler flags.

The attachment containes the result  of: gdb -ex "thread apply all bt" --batch /usr/sbin/asterisk `pidof asterisk` > /tmp/backtrace-threads.txt

another file in the attachment is what I see on the screen while performing : asterisk -rx "core show locks" > /tmp/core-show-locks.txt

Test Scenario:

my Perl daemon once in 3 seconds sends QueueStatus AMI reques and receives no reply. In fact I can issue the same Queue show command in the console but I get no reply either

                
> Queues on virtual machines
> --------------------------
>
>                 Key: ASTERISK-20718
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20718
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_queue
>    Affects Versions: 1.8.15.0
>         Environment: Asterisk 1.8.11 cert8/Centos 5.8 on VirtualBOX, Asterisk 1.8.11 cert8/Debian 6 on Virtual BOX, Asterisk 1.8.11 cert8/Centos 6.3, Asterisk 1.8.15/Centos 5.8 on VirtualBOX, Asterisk 1.8.15/Debian 6 on Virtual BOX, Asterisk 1.8.15/Centos 6.3, Asterisk 1.8.15/Hyper-V, Asterisk 1.8.11/Hyper-V
>            Reporter: Roberto
>            Assignee: Roberto
>         Attachments: backtrace-threads.rar
>
>
> When invoke QueueAdd function through telnet by 5038 port Asterisk it doesn't response and then, if invoke "queue show" on Asterisk CLI it crashes and no more actions can be made. Don't know if the problem occurs only  on virtual machines but it occurs on every development enviroment i've tried.

--
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