head 1.2; access; symbols RPM_4_2_1:1.1.1.5 RPM_4_2:1.1.1.5 RPM_4_1_1:1.1.1.5 RPM_4_1:1.1.1.4 RPM_4_0_5:1.1.1.3 RPM_4_0_4:1.1.1.2 RPM_4_0_3:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.2 date 2008.01.02.09.53.58; author rse; state dead; branches; next 1.1; commitid z4cpSiAhOCXk5PLs; 1.1 date 2001.07.23.20.45.37; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2001.07.23.20.45.37; author rse; state Exp; branches; next 1.1.1.2; 1.1.1.2 date 2002.01.08.00.30.10; author rse; state Exp; branches; next 1.1.1.3; 1.1.1.3 date 2003.01.18.13.49.00; author rse; state Exp; branches; next 1.1.1.4; 1.1.1.4 date 2001.12.06.00.08.10; author rse; state Exp; branches; next 1.1.1.5; 1.1.1.5 date 2003.01.18.14.04.58; author rse; state Exp; branches; next ; desc @@ 1.2 log @remove the ancient RPM 4.2.1 source tree copy @ text @ Berkeley DB: DbEnv.set_lk_max_lockers

DbEnv.set_lk_max_lockers

APIRef

import com.sleepycat.db.*;

public void set_lk_max_lockers(int max) throws DbException;

Description

Set the maximum number of simultaneous locking entities supported by the Berkeley DB lock subsystem. This value is used by DbEnv.open to estimate how much space to allocate for various lock-table data structures. The default value is 1000 lockers. For specific information on configuring the size of the lock subsystem, see Configuring locking: sizing the system.

The DbEnv.set_lk_max_lockers interface may be used only to configure Berkeley DB before the DbEnv.open interface is called.

The DbEnv.set_lk_max_lockers method throws an exception that encapsulates a non-zero error value on failure.

The database environment's maximum number of lockers may also be set using the environment's DB_CONFIG file. The syntax of the entry in that file is a single line with the string "set_lk_max_lockers", one or more whitespace characters, and the number of lockers. Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.

Errors

The DbEnv.set_lk_max_lockers method may fail and throw an exception encapsulating a non-zero error for the following conditions:

EINVAL
An invalid flag value or parameter was specified.

Called after DbEnv.open was called.

The DbEnv.set_lk_max_lockers method may fail and throw an exception for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the DbEnv.set_lk_max_lockers method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

DbEnv, DbLock

See Also

DbEnv.set_lk_conflicts, DbEnv.set_lk_detect, DbEnv.set_lk_max, DbEnv.set_lk_max_lockers, DbEnv.set_lk_max_locks, DbEnv.set_lk_max_objects, DbEnv.lock_detect, DbEnv.lock_get, DbEnv.lock_id, DbLock.put, and DbEnv.lock_stat.

APIRef

Copyright Sleepycat Software @ 1.1 log @Initial revision @ text @d1 1 a1 1 @ 1.1.1.1 log @Import: RPM 4.0.3 @ text @@ 1.1.1.2 log @Import: RPM 4.0.4 @ text @d1 1 a1 1 d17 1 a17 1 APIRef d25 1 a25 1 throws DbException; d60 1 d67 1 a67 2 DbEnv.lock_id_free, DbEnv.lock_put, d72 1 a72 1 APIRef @ 1.1.1.3 log @Import: RPM 4.0.5 @ text @d1 2 a2 2 a3 1 d35 2 a36 7

The DbEnv.set_lk_max_lockers method configures a database environment, not only operations performed using the specified DbEnv handle.

The DbEnv.set_lk_max_lockers interface may not be called after the DbEnv.open interface is called. If the database environment already exists when DbEnv.open is called, the information specified to DbEnv.set_lk_max_lockers will be ignored. d52 3 a54 3 If a catastrophic error has occurred, the DbEnv.set_lk_max_lockers method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d56 1 a56 1 DbEnv, DbLock d58 12 a69 1 Locking Subsystem and Related Methods @ 1.1.1.4 log @Import: RPM 4.1 @ text @d1 2 a2 2 d4 1 d36 7 a42 2

The DbEnv.set_lk_max_lockers interface may be used only to configure Berkeley DB before the DbEnv.open interface is called. d58 3 a60 3 If a catastrophic error has occurred, the DbEnv.set_lk_max_lockers method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d62 1 a62 1 DbEnv, DbLock d64 1 a64 12 DbEnv.set_lk_conflicts, DbEnv.set_lk_detect, DbEnv.set_lk_max_lockers, DbEnv.set_lk_max_locks, DbEnv.set_lk_max_objects, DbEnv.lock_detect, DbEnv.lock_get, DbEnv.lock_id, DbEnv.lock_id_free, DbEnv.lock_put, and DbEnv.lock_stat. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d35 2 a36 7

The DbEnv.set_lk_max_lockers method configures a database environment, not only operations performed using the specified DbEnv handle.

The DbEnv.set_lk_max_lockers interface may not be called after the DbEnv.open interface is called. If the database environment already exists when DbEnv.open is called, the information specified to DbEnv.set_lk_max_lockers will be ignored. d52 3 a54 3 If a catastrophic error has occurred, the DbEnv.set_lk_max_lockers method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d56 1 a56 1 DbEnv, DbLock d58 12 a69 1 Locking Subsystem and Related Methods @