[#CORE-2640] A regular deadlock may not be detected by the lock manager under some conditions, thus resulting in a hang

Firebird Core

A regular deadlock may not be detected by the lock manager under some conditions, thus resulting in a hang

Created: 25/Sep/09 04:14 AM Updated: 12/Nov/09 05:44 PM

Return to search

Component/s:

Engine

Affects Version/s:

2.0.5, 2.1.2, 2.5 Beta 1, 2.5 Beta 2, 2.1.3

Fix Version/s:

2.5 RC1, 2.0.6, 2.1.4

Time Tracking:

Not Specified

Issue Links:

Relate

This issue is related to:

~~CORE-2000~~ Lock manager reported false deadlocks under high load

Planning Status:

Unspecified

Description

« Hide

It seems that the fix for ~~CORE-2000~~ was incomplete and may cause a hang if the just granted request doesn't have an assigned AST routine. In this case, it happened for transaction locks: transactions A and B wait for each others uncommitted versions and no deadlock is reported after the default interval of 10 seconds.

All

Comments

Work Log

Change History

Version Control

Sort Order:

The cvs commits can not be displayed for repository Firebird at the moment since the log has not yet been parsed. The log will be parsed the next time the VcsService runs. If you have administrators privileges you can hasten the next time the service will run in the service section of the Administration pages.