[asterisk-bugs] [Asterisk 0012880]: Queue() uses cached information to determine whether queue is empty or not

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12880 
====================================================================== 
Reported By:                bcnit
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12880
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.0-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 suspended
Fixed in Version:           
====================================================================== 
Date Submitted:             06-18-2008 02:24 CDT
Last Modified:              07-01-2008 11:31 CDT
====================================================================== 
Summary:                    Queue() uses cached information to determine whether
queue is empty or not
Description: 

If I have a queue which is driven by realtime and Asterisk is not aware of
the queue (i.e. 'queue show' shows nothing), then if the queue is set with
'joinempty=no', when you try to queue a call to it, Asterisk bounces the
call out with QUEUESTATUS as JOINEMPTY.

Once Asterisk knows of the queue's existance, then realtime is checked to
see if the queue is empty or not and all works fine.

The only way I can get around this is to run a script when Asterisk starts
which interrogates the database to get the list of all queues run by
realtime and then issue an 'asterisk -rx "queue show QUEUE"' for each one
to populate the cache.

Please see bug report http://bugs.digium.com/view.php?id=12858 to which this is
probably related.

====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 07-01-08 11:31  
---------------------------------------------------------------------- 
I have a sneaking suspicion that this issue is actually the same as what's
happening in http://bugs.digium.com/view.php?id=12884. That, coupled with the
fact that I haven't heard any
feedback on the patch, is prompting me to suspend this. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-01-08 11:31  putnopvut      Status                   assigned => resolved
07-01-08 11:31  putnopvut      Resolution               open => suspended   
07-01-08 11:31  putnopvut      Note Added: 0089535                          
======================================================================