| Summary: | ASTERISK-20162: app_queue does no Status update on empty SQL result | ||||
| Reporter: | Ronny Becker (bioasterisk) | Labels: | |||
| Date Opened: | 2012-07-23 01:02:04 | Date Closed: | 2012-07-25 17:35:20 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | Applications/app_queue Resources/res_realtime | ||
| Versions: | 1.8.13.0 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Debian 6, 64bit | Attachments: | |||
| Description: | Using the realtime queue_member_table. Everything is fine as long as you have users for the queue in the table. If you delete the last user or of you delete all users at once, there is no update on the queue Status made. The Problem is: [Jul 23 07:49:39] DEBUG[10242] res_config_mysql.c: MySQL RealTime: Connection okay. [Jul 23 07:49:39] DEBUG[10242] res_config_mysql.c: MySQL RealTime: Retrieve SQL: SELECT * FROM queue_member_table WHERE interface LIKE '%' AND queue_name = 'bsimoe' ORDER BY interface [Jul 23 07:49:39] DEBUG[10242] app_queue.c: Queue bsimoe has no realtime members defined. No need for update If the SQL Query returns no result, there is no update made to the queue Status and all members that have been in the queue remain there. It has to remove all members of a queue if the SQL Query returns nothing. This Bug came into asterisk between 1.8.7(works) and 1.8.13. | ||||
| Comments: | By: Rusty Newton (rnewton) 2012-07-25 17:35:20.805-0500 Closing as duplicate of ASTERISK-19793 which is already in progress. Please comment on 19793 for any additional information beyond what you have here. I'll link the other issue to this one. | ||||