Kbase 15617: SE: uc_wait is not 0 when utlockdb is called, user (1070)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
SE: uc_wait is not 0 when utlockdb is called, user (1070)
This notebook entry deals with the following error.
SYSTEM ERROR: uc_wait is not 0 when utlockdb is called, user (1070)
What does this message mean?
A process is attempting to acquire the DB lock but has found a lock
conflict; it then has to wait for the DB lock. At the same time, this
same process is also waiting to acquire some other resource that it is
queued for. This condition creates an internal inconsistency.
The code has been rewritten between versions 6.2, 6.3, and V7. There
may be slight differences in the way some of this code is implemented
in each version, but the error always indicates that an internal
inconsistency occurred.
This is a bug. If this error occurs in the latest PROGRESS version
for a platform, it should be logged as a bug, escpecially if it is
recurring.
4-Mar-96
Progress Software Technical Support Note # 15617