Kbase P23545: When the remote client crashes, the record stays locked on the db server
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/12/2008 |
|
Status: Verified
SYMPTOM(s):
When the remote client crashes, the record stays locked on the db server
Records remain locked after remote client crashes
If the 4GL remote client crashes, then the records that were locked by that user remain locked in the database
Using remote client network connection to the database server
FACT(s) (Environment):
All Supported Operating Systems
Progress 7.x
Progress 8.x
Progress 9.x
CAUSE:
The remote server will keep the record(s) locked until it gets the TCP KeepAlive timeout signaling that the client connection has been terminated.
FIX:
This behavior is inherent due to the implementation of the TCP network protocol.
Reduce the TCP KeepAlive timeout from the 2 hour default setting to 15 minutes to minimize the problem.