Bug #259
Lock callback mechanism
| Status: | Closed | Start date: | 06/11/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: |
Description
Right now, when a pool needs to access the DB, it sets the callback function and then asks the DB to perform the query.
The DB then locks its mutex, performs the query, calls back the pool, and unlocks itself.
If this sql query takes too much time, the pool may set a new callback function hoping to perform a new query. In this case the first query answer is sent to the wrong callback function.
Associated revisions
bug #259: Callback functions are locked until the DB query answer is processed.
History
#1
Updated by Ruben S. Montero about 11 years ago
- Status changed from New to Closed
- Resolution set to fixed
Now in master