Kbase P55194: Client keeps waiting on record lock release
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/06/2008 |
|
Status: Verified
SYMPTOM(s):
Client keeps waiting on record lock release
<file-name> in use by <user> on <tty>. Wait or press <STOP> to stop. (121)
<file-name> in use by <user> on <tty>. Wait or choose CANCEL to stop. (2624)
Multiple clients accessing same table using same index
Table is accessed with a FOR EACH ... EXCLUSIVE-LOCK
One client changes a key field in a record, making it invalid for the selection provided in the other clients. This client may or may not use a different index.
FACT(s) (Environment):
Progress 9.1x
All Supported Operating Systems
CAUSE:
Bug# OE00097706
CAUSE:
Under specific circumstances, when three or more clients are in contention for an exclusive lock, one of the clients may fail to "wake up" from waiting even when the record is available for that client.
FIX:
Upgrade to Progress 9.1D08, OpenEdge 10.0A or later release
Workaround:
Use SHARE-LOCK instead of EXCLUSIVE-LOCK.
The way a SHARE-LOCK is handled ensures the client does not hang.