[asterisk-bugs] [Asterisk 0006982]: [patch] load_realtime_queue with dbconfig overrides dynamic configuration

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=6982 
====================================================================== 
Reported By:                j
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   6982
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): trunk 
SVN Revision (number only!):  
Disclaimer on File?:        Yes 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             04-17-2006 15:48 CDT
Last Modified:              08-30-2007 17:39 CDT
====================================================================== 
Summary:                    [patch] load_realtime_queue with dbconfig overrides
dynamic configuration
Description: 
Greetings

  I noticed that if you use an sql DB for queue configuration and also use
the asterisk manager interface to configure members dynamically, the
dynamic changes are overridden when certain events occur, such as executing
'show queues' with a queue name given, or any time someone joins the
queue.

  I understand the importance of being able to update the configuration of
a queue from a database in real time, yet using the asterisk manager
interface to configure queues on-the-fly is also an important feature. Is
there some harmony that can be acheived between the two?

  I've supplied a small patch that *sort of* solves the problem.

  In 1.2.7.1 (stable) [my apologies, the version drop-down doesn't have
this version in it yet] I simply told the load_realtime_queue function that
if the queue already exists, don't load it from the database. This allows
the queues to be loaded as needed (as they were before), but makes sure
they're not overridden by loading them again even if they're already in
memory.

  Perhaps you guys have a better solution?
  If the DB overrides queues that already exist in memory, this makes most
of the functionality in the asterisk manager interface quite useless :(

  Thanks

j
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 08-30-07 17:39  
---------------------------------------------------------------------- 
I just tested this in 1.4 (latest SVN, r81397) and it works fine. If
further problems arise this can be reopened. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-30-07 17:39  putnopvut      Status                   acknowledged => resolved
08-30-07 17:39  putnopvut      Resolution               open => fixed       
08-30-07 17:39  putnopvut      Assigned To               => putnopvut       
08-30-07 17:39  putnopvut      Note Added: 0069755                          
======================================================================