Release 10.1A: OpenEdge Deployment:
Startup Command and Parameter Reference

> ## Lock Timeout (-lkwtmo)

> Use Lock Timeout (`-lkwtmo`) to specify a different wait time (in seconds).

> Operating system and syntax | UNIX Windows | `-lkwtmo` `seconds`
> Use with | Maximum value | Minimum value | Single-user default | Multi-user default
> Client Session | – | 60 | 18001 | 18001

> 1The default wait time for WebSpeed is 10 seconds.

> ``seconds``

> The 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. This feature is called “lock wait timeout.”

> The default wait time is 1800 seconds (30 minutes). The minimum value is 60 seconds. If a user specifies a value less than 60 seconds, Progress silently sets the value at 60 seconds.

> Note: The wait time is accurate to within one minute of the value specified.

> Lock timeout applies to interactive and batch clients."The client gets a `STOP` condition if this value is exceeded on the AppServer. For more information, see the sections on client/server conflicts in OpenEdge Application Server: Developing AppServer Applications .

> Lock timeout affects `WAIT-FOR` record locks, schema locks, and transaction commit locks. Lock timeout does not affect internal locks used inside the database manager, such as buffer locks.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095