Kbase 13881: What is the Bleeding Record Lock Problem? -brl
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
What is the Bleeding Record Lock Problem? -brl
Bleeding Record Lock Problem--what is it?
-----------------------------------------
This issue has existed since the very early versions of
Progress. The essence is that sometimes record locks are
held longer than they should be when a record is used by
more than one buffer. More specifically, a share lock on a
record may persist even though no transaction is active
and the only buffer which used it shared, of the 2 or more
that held the record, has released it.
Why fix it now?
---------------
With the introduction of persistent procedures it will be
easier to create the bleeding lock situation and harder to
diagnose it. The scope of a record buffer used in a
persistent procedure is likely to last for a longer period
of time.
What version is it fixed in?
----------------------------
The bleeding lock issue has been fixed in version 7.3B. It
is a client side fix and NOT a server fix. The fixed
behavior is the default behavior in version 7.3B. Users who
do not want the problem fixed in their applications
for backwards compatibility will be able to use a startup
option to get the old behavior. The startup option is -brl.
There is no workaround for this issue in Progress versions
prior to version 7.3B.
Progress Software Technical Support Note # 13881