Kbase P116284: Why does a remote client wait 2 to 4 seconds to obtain an exclusive lock held by another user?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/05/2010 |
|
Status: Verified
GOAL:
Why does a remote client wait 2 to 4 seconds to obtain an exclusive lock held by another user?
FACT(s) (Environment):
Progress/OpenEdge Product Family
All Supported Operating Systems
CAUSE:
Enhancement Request# 3414
FIX:
This Enhancement has not been implemented in the product.
Remote clients may wait anywhere from 2 to 4 seconds on average in situations when requesting locks on a record(s).
If a remote client can not acquire a lock on a record it will check every 2 seconds to see if the lock is available (this is designed to reduce network traffic).