[Asterisk-bugs] [Asterisk 0009618]: When Using Multiple Queues, Agent Status Gets Stuck As "Busy" In Select Queues

[noreply at bugs.diguim.com]

email_notification_title_for_action_bugnote_submitted 
====================================================================== 
http://bugs.digium.com/view.php?id=9618 
====================================================================== 
Reported By:                jiddings
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   9618
Category:                   Applications/app_queue
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:            SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 62174 
Disclaimer on File?:        No 
Request Review:              
====================================================================== 
Date Submitted:             04-27-2007 16:04 CDT
Last Modified:              06-29-2007 15:16 CDT
====================================================================== 
Summary:                    When Using Multiple Queues, Agent Status Gets Stuck
As "Busy" In Select Queues
Description: 
Scenario..

Agent/1000 is logged in using AgentLogin() via a SIP phone..  Agent/1000
is a member of 15 queues, all using "leastrecent" as as strategy, and
"ringinuse=no". Agent/1000 will randomly stop getting calls for select
queues, and is shown as "busy" when in queue X, but available in queue Y.
The busy state for queue X will not change until the agent logs out and
back in again.
====================================================================== 

---------------------------------------------------------------------- 
 dimas - 06-29-07 15:16  
---------------------------------------------------------------------- 
jiddings,
are you sure the "the console debug information when the problem occurs"
actually gets print only when the problem really occurs?
As far as I can tell from the sources, this "error" gets printed any time
when one threads waits for mutex more than 5 seconds. And the message is
repeated every 5 seconds. 
One of chan_agent mutexes is kept locked for the whole duration of call
while the thread handling AgentLogin application tries to lock it
(generating the message). 
That is why I do not see any problem with this particular error message
and I do not think it ever relates to the problem.

(Well, to me, conditional variable should be used instead of mutex there
and prevent that error-message-flood but that is completely different
story) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-27-07 16:04  jiddings       New Issue                                    
04-27-07 16:04  jiddings       Issue Monitored: jiddings                    
04-27-07 16:04  jiddings       Asterisk Version          =>  SVN            
04-27-07 16:04  jiddings       SVN Branch (only for SVN checkou =>  1.4         
  
04-27-07 16:04  jiddings       SVN Revision (number only!) => 62174           
04-27-07 16:04  jiddings       Disclaimer on File?       => No              
04-30-07 22:47  r00ted         Issue Monitored: r00ted                      
05-02-07 09:26  jiddings       Note Added: 0062968                          
05-02-07 10:34  jiddings       Note Added: 0062971                          
05-02-07 12:34  jiddings       Note Added: 0062975                          
05-02-07 13:14  jiddings       Note Added: 0062980                          
05-02-07 14:07  explidous      Issue Monitored: explidous                    
05-02-07 16:14  jiddings       Note Added: 0062993                          
05-02-07 17:45  jiddings       Note Added: 0062998                          
05-02-07 19:51  jiddings       Note Added: 0063006                          
05-02-07 21:16  russell        File Added: deadlock.txt                     
05-03-07 09:50  russell        Issue Monitored: russell                     
05-03-07 10:21  jiddings       Note Deleted: 0063006                        
05-03-07 10:22  jiddings       Note Deleted: 0062975                        
05-03-07 10:22  jiddings       Note Deleted: 0062980                        
05-03-07 10:23  jiddings       Note Edited: 0062993                         
05-03-07 13:33  jiddings       Note Added: 0063045                          
05-03-07 13:58  jiddings       File Added: backtrace.txt                    
05-03-07 14:00  jiddings       Note Added: 0063048                          
05-10-07 05:09  simek          Issue Monitored: simek                       
06-06-07 20:20  rflopes3       Note Added: 0064700                          
06-06-07 20:22  rflopes3       Note Added: 0064701                          
06-22-07 15:19  ekreckel       Note Added: 0065599                          
======================================================================