If some process acquire fast mutex and died not releasing it it could hung all other activity.
Fast mutex was contributed by Yaffil team and integrated into Firebird 2.1. Since that time there was no reports about issues related to fast mutex robustness.
I reproduced hung in very specific scenario and only as result of another bug (see CORE-3325).
Description
If some process acquire fast mutex and died not releasing it it could hung all other activity.
Fast mutex was contributed by Yaffil team and integrated into Firebird 2.1. Since that time there was no reports about issues related to fast mutex robustness.
I reproduced hung in very specific scenario and only as result of another bug (see CORE-3325).
Well, the hanging happened quite regularly if you have 100's of users on a faulty network.
For Firebird 2.1 the hanging was reported once or twice a year per each 1000 connected users
Nickolay Samofatov added a comment - 02/Feb/11 01:01 PM Well, the hanging happened quite regularly if you have 100's of users on a faulty network.
For Firebird 2.1 the hanging was reported once or twice a year per each 1000 connected users
CORE-3153 is the earlier incarnation of this bug
Vlad Khorsun added a comment - 02/Feb/11 02:17 PM So far, you are the only one who reported such issue.
BTW, could you review the fix and, if possible, test it ?
Bug
Closed
Major
Fast mutex could be left in locked state by dead process
For Firebird 2.1 the hanging was reported once or twice a year per each 1000 connected users
CORE-3153is the earlier incarnation of this bug