| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
however, this had no negative effect, as the message processing state
was not evaluated when a batch was deleted, and that was the only case
where the state could be wrong.
|
| |
|
|
|
|
|
|
|
|
| |
simplified and thus speeded up the queue engine, also fixed some
potential race conditions (in very unusual shutdown conditions)
along the way. The threading model has seriously changes, so there may
be some regressions.
NOTE: the code passed basic tests, but there is still more work
and testing to be done. This commit should be treated with care.
|
| |
|
|
| |
... non-working version!
|
| |
|
|
|
|
|
|
| |
- bugfix: solved potential (temporary) stall of messages when the queue was
almost empty and few new data added (caused testbench to sometimes hang!)
- fixed some race condition in testbench
- added more elaborate diagnostics to parts of the testbench
- solved a potential race inside the queue engine
|
| |
|
|
| |
The enhanced testbench now runs without failures, again
|
| |
|
|
| |
slightly improved situation, would like to save it before carrying on
|
|
|
... and now make check fails again, we have obviously found some new
bugs thanks to the additional cases
|
