Edit File - File Manager

Edit File: lock_vec.html

<html>
<head>
<title>Berkeley DB: DbEnv::lock_vec</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<table width="100%"><tr valign=top>
<td>
DbEnv::lock_vec
</td>
<td align=right>
<a href="../../db4-devel-4.7.25/api_cxx/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a>
<a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a></td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>
#include &lt;db_cxx.h&gt;

int
DbEnv::lock_vec(u_int32_t locker, u_int32_t flags,
 DB_LOCKREQ list[], int nlist, DB_LOCKREQ **elistp);
</pre>
<hr size=1 noshade>
Description: DbEnv::lock_vec
The DbEnv::lock_vec method atomically obtains and releases one or more locks
from the lock table. The DbEnv::lock_vec method is intended to support
acquisition or trading of multiple locks under one lock table semaphore,
as is needed for lock coupling or in multigranularity locking for lock
escalation.
If any of the requested locks cannot be acquired, or any of the locks to
be released cannot be released, the operations before the failing
operation are guaranteed to have completed successfully, and
DbEnv::lock_vec returns a non-zero value. In addition, if
elistp is not NULL, it is set to point to the DB_LOCKREQ entry
that was being processed when the error occurred.
Unless otherwise specified, the DbEnv::lock_vec method
either returns a non-zero error value
or throws an exception that encapsulates a non-zero error value on
failure, and returns 0 on success.

Parameters 
 elistp<ul compact><li>If an error occurs, and the elistp parameter is non-NULL, it
is set to point to the DB_LOCKREQ entry that was being processed when
the error occurred.</ul>
 flags<ul compact><li>The flags parameter must be set to 0 or
the following value:
 
<a name="DB_LOCK_NOWAIT">DB_LOCK_NOWAIT</a><ul compact><li>If a lock cannot be granted because the requested lock conflicts with
an existing lock,
return DB_LOCK_NOTGRANTED or throw a
<a href="../../db4-devel-4.7.25/api_cxx/lockng_class.html">DbLockNotGrantedException</a> immediately instead of waiting for
the lock to become available. In this case, if non-NULL,
elistp identifies the request that was not granted, or, if an
exception is thrown, the index of the request that was not granted can
be found by calling DbLockNotGrantedException.get_index.</ul>
 </ul>
 locker<ul compact><li>The locker parameter is an unsigned 32-bit integer quantity. It
represents the entity requesting or releasing the lock.</ul>
 list<ul compact><li>The list array provided to DbEnv::lock_vec is typedef'd as
DB_LOCKREQ.
To ensure compatibility with future releases of Berkeley DB, all
fields of the DB_LOCKREQ structure that are not explicitly set should
be initialized to 0 before the first time the structure is used. Do
this by declaring the structure external or static, or by calling
memset(3).
A DB_LOCKREQ structure has at least the following fields:
 
lockop_t <a name="op">op</a>;<ul compact><li>The operation to be performed, which must be set to one of the
following values:</ul>
 
<a name="DB_LOCK_GET">DB_LOCK_GET</a><ul compact><li>Get the lock defined by the values of the mode and obj
structure fields, for the specified locker. Upon return from
DbEnv::lock_vec, if the lock field is non-NULL, a reference
to the acquired lock is stored there. (This reference is invalidated
by any call to DbEnv::lock_vec or <a href="../../db4-devel-4.7.25/api_cxx/lock_put.html">DbEnv::lock_put</a> that releases the
lock.)</ul>
<a name="DB_LOCK_GET_TIMEOUT">DB_LOCK_GET_TIMEOUT</a><ul compact><li>Identical to DB_LOCK_GET except that the value in the timeout
structure field overrides any previously specified timeout value for
this lock. A value of 0 turns off any previously specified timeout.</ul>
<a name="DB_LOCK_PUT">DB_LOCK_PUT</a><ul compact><li>The lock to which the lock structure field refers is released.
The locker parameter, and mode and obj fields
are ignored.</ul>
<a name="DB_LOCK_PUT_ALL">DB_LOCK_PUT_ALL</a><ul compact><li>All locks held by the specified locker are released. The
lock, mode, and obj structure fields are
ignored. Locks acquired in operations performed by the current call to
DbEnv::lock_vec which appear before the DB_LOCK_PUT_ALL
operation are released; those acquired in operations appearing after
the DB_LOCK_PUT_ALL operation are not released.</ul>
<a name="DB_LOCK_PUT_OBJ">DB_LOCK_PUT_OBJ</a><ul compact><li>All locks held on obj are released. The locker
parameter and the lock and mode structure fields are
ignored. Locks acquired in operations performed by the current call to
DbEnv::lock_vec that appear before the DB_LOCK_PUT_OBJ
operation are released; those acquired in operations appearing after the
DB_LOCK_PUT_OBJ operation are not released.</ul>
<a name="DB_LOCK_TIMEOUT">DB_LOCK_TIMEOUT</a><ul compact><li>Cause the specified locker to timeout immediately. If the
database environment has not configured automatic deadlock detection,
the transaction will timeout the next time deadlock detection is
performed. As transactions acquire locks on behalf of a single locker
ID, timing out the locker ID associated with a transaction will time
out the transaction itself.</ul>
 
DB_LOCK <a name="lock">lock</a>;<ul compact><li>A lock reference.</ul>
const lockmode_t <a name="mode">mode</a>;<ul compact><li>The lock mode, used as an index into the environment's lock conflict matrix.
When using the default lock conflict matrix, mode must be set to one
of the following values:
 
<a name="DB_LOCK_READ">DB_LOCK_READ</a><ul compact><li>read (shared)</ul>
<a name="DB_LOCK_WRITE">DB_LOCK_WRITE</a><ul compact><li>write (exclusive)</ul>
<a name="DB_LOCK_IWRITE">DB_LOCK_IWRITE</a><ul compact><li>intention to write (shared)</ul>
<a name="DB_LOCK_IREAD">DB_LOCK_IREAD</a><ul compact><li>intention to read (shared)</ul>
<a name="DB_LOCK_IWR">DB_LOCK_IWR</a><ul compact><li>intention to read and write (shared)</ul>
 
See <a href="../../db4-devel-4.7.25/api_cxx/env_set_lk_conflicts.html">DbEnv::set_lk_conflicts</a> and <a href="../../db4-devel-4.7.25/ref/lock/stdmode.html">Standard Lock Modes</a> for more information on the lock conflict matrix.</ul>
const Dbt <a name="obj">obj</a>;<ul compact><li>An untyped byte string that specifies the object to be locked or
released. Applications using the locking subsystem directly while also
doing locking via the Berkeley DB access methods must take care not to
inadvertently lock objects that happen to be equal to the unique file
IDs used to lock files. See <a href="../../db4-devel-4.7.25/ref/lock/am_conv.html">Access
method locking conventions</a> for more information.</ul>
u_int32_t timeout;<ul compact><li>The lock timeout value.</ul>
 </ul>
 nlist<ul compact><li>The nlist parameter specifies the number of elements in the
list array.</ul>
 
 Errors
The DbEnv::lock_vec method
may fail and throw
<a href="../../db4-devel-4.7.25/api_cxx/except_class.html">DbException</a>,
encapsulating one of the following non-zero errors, or return one of
the following non-zero errors:
 
EINVAL<ul compact><li>An
invalid flag value or parameter was specified.</ul>
 
If a transactional database environment operation was selected to
resolve a deadlock, the DbEnv::lock_vec method will fail and
either return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_LOCK_DEADLOCK">DB_LOCK_DEADLOCK</a> or
throw a <a href="../../db4-devel-4.7.25/api_cxx/deadlock_class.html">DbDeadlockException</a> exception.
If a Berkeley DB Concurrent Data Store database environment configured for lock timeouts was unable
to grant a lock in the allowed time, the DbEnv::lock_vec method will fail and
either return <a href="../../db4-devel-4.7.25/ref/program/errorret.html#DB_LOCK_NOTGRANTED">DB_LOCK_NOTGRANTED</a> or
throw a <a href="../../db4-devel-4.7.25/api_cxx/lockng_class.html">DbLockNotGrantedException</a> exception.
If the <a href="../../db4-devel-4.7.25/api_cxx/lock_vec.html#DB_LOCK_NOWAIT">DB_LOCK_NOWAIT</a> flag or lock timers were configured and the lock could not be granted before the wait-time expired,
the DbEnv::lock_vec method will fail and
either return DB_LOCK_NOTGRANTED or
throw a <a href="../../db4-devel-4.7.25/api_cxx/lockng_class.html">DbLockNotGrantedException</a> exception.
If the maximum number of locks has been reached, the DbEnv::lock_vec method will fail and
either return ENOMEM or
throw a DbMemoryException.
<hr size=1 noshade>
 Class
<a href="../../db4-devel-4.7.25/api_cxx/env_class.html">DbEnv</a>, <a href="../../db4-devel-4.7.25/api_cxx/lock_class.html">DbLock</a>
 See Also
<a href="../../db4-devel-4.7.25/api_cxx/lock_list.html">Locking Subsystem and Related Methods</a>
</tt>
<table width="100%"><tr><td> </td><td align=right>
<a href="../../db4-devel-4.7.25/api_cxx/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a><a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager