[asterisk-bugs] [JIRA] (ASTERISK-17049) [patch]Setting linear queue strategy requires asterisk restart

[Diego Kappa (JIRA)]

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

Diego Kappa edited comment on ASTERISK-17049 at 3/4/15 9:44 AM:
----------------------------------------------------------------

Created:	01/Dec/10 6:15 AM and it still opened?

Of course you can't say this is a bug because of the weak restart log message, but I really think this must be solved.
At least you can edit to allow to use a FLAG on compiling time to choose between all these free memory you get when you don't keep the order, or keep order and change strategies without restarts

Is anyone following this thread?

I love who made the patch, but I'm really interested to make official this patch.
I'm using Asterisk 13 and it still the same issue


was (Author: dcapape):
Created:	01/Dec/10 6:15 AM and it still opened?

Of course you can't say this is a bug because of the weak restart log message, but I really think this must be solved.
At least you can edit to allow to use a FLAG on compiling time to choose between all these free memory you get when you don't keep the order, or keep order and change strategies without restarts

Is anyone following this thread?

I love who made the patch, but I'm really interested to make official this patch.

> [patch]Setting linear queue strategy requires asterisk restart
> --------------------------------------------------------------
>
>                 Key: ASTERISK-17049
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17049
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Applications/app_queue
>    Affects Versions: 1.8.4
>            Reporter: Vadim Mikhnevych
>            Severity: Minor
>         Attachments: app_queue_linear_17049.patch, app_queue_linear_v2.patch, linear_update_11.5.patch
>
>
> Currently (also in 1.8.0): "Changing to the linear strategy currently requires asterisk to be restarted."
> Though it can be proudly represented as a "feature, not a bug", I don't think this behaviour is suitable for 24/7 systems where users can often change their settings. In this case asterisk restart would hangup all active calls, which is a BAD THING. (This part is more like a feature request, and the bug goes below)
> So, here goes the bug:
> According to app_queue.c sources, this message occurs only for realtime. And, actually, one can't see this message if queue strategy was changed in queues.conf. 
> But, after altering queues config file and invoking either "config reload /etc/asterisk/queues.conf" or "queues reload all", members order in queue is not the same as in .conf file, and incoming calls are routed to queue members also in wrong order.
> PS If used strategy is set to "linear" and asterisk is restarted, order of members in queue and config file is the same, and the bug doesn't reproduce. 
> Of course, adding a message "Please, restart asterisk" for static configuration reload wouldn't be a best solution. I'd prefer not to restart asterisk at all.



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