Issue Details (XML | Word | Printable)

Key: CORE-1881
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dmitry Yemanov
Reporter: Dmitry Yemanov
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
Firebird Core

Database monitoring may crash the server or badly affect its page locking logic

Created: 05/May/08 01:59 AM   Updated: 18/Nov/08 12:50 PM
Component/s: Engine
Affects Version/s: 2.5 Initial, 2.1.0
Fix Version/s: 2.5 Alpha 1, 2.1.1

Environment: Any

Planning Status: Included to release
Target: 2.5 Alpha 1 and 2.1.1

 Description  « Hide
The monitoring code unconditionally fetches the header page to report the actual database state. But, if being done at the AST level, this may cause two concurrent pending requests being linked to a single owner. The lock manager highly dislikes this situation and terminates the process via a bugcheck.

It can be reproduced under high load with the SuperClassic architecture. So far I was unable to see this issue on v2.1 Classic, maybe it could be explained by different synchronization techniques used. But anyway, I mark v2.1.0 as possibly affected and the fix will be committed into both branches.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.