Use the Lock Timeout (
-lkwtmo) client session parameter to specify a different record lock wait time (in seconds).
An OpenEdge process encountering a locked resource, waits for a limited time before continuing execution. If the resource is still locked, the process times out and the wait is canceled by the STOP condition. This feature is called “
lock wait timeout".
When a lock on a record times out, the WAIT will be canceled and the effect will be exactly the same as if an interactive user had pressed CANCEL in GUI mode or CONTROL-C in character mode in the 2624 alert .
Defaults:
- The default wait time is 1800 seconds (30 minutes) for all clients except WebSpeed agents the default lock wait timeout is 10 seconds
- The minimum value is 10 seconds.
- The wait time is accurate to within one minute of the value specified.
- Lock timeout applies to interactive and batch clients and component server processes.
- Lock timeout affects WAIT-FOR record locks, schema locks, and transaction commit locks.
- Lock timeout is only raised when the NO-WAIT option is not used, because a NO-WAIT will raise an ERROR, not STOP.
- Lock timeout does not affect internal locks used inside the database manager, such as buffer locks.
Usage example : To increase this interval add
-lkwtmo the parameter and it's value in the Agent's startup parameters.
[UBroker.AS.asbroker1]
appserviceNameList=asbroker1
brkrDebuggerKeyAlias=default_server
brokerLogFile=@{WorkPath}\asbroker1.broker.log
controllingNameServer=NS1
defaultService=1
description=A sample AppServer setup for State-reset
environment=asbroker1
keyAlias=default_server
password=
portNumber=3090
srvrLogFile=@{WorkPath}\asbroker1.server.log
srvrStartupParam=-lkwtmo 1800
userName=
uuid=932.99.999.XXX:1ee77e:cf3bbe3d33:-8000
