Edit File - File Manager

Edit File: env_set_thread_id.html

<html>
<head>
<title>Berkeley DB: DB_ENV-&gt;set_thread_id</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>
DB_ENV-&gt;set_thread_id
</td>
<td align=right>
<a href="../../db4-devel-4.7.25/api_c/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.h&gt;

int
DB_ENV-&gt;set_thread_id(DB_ENV *dbenv,
 void (*thread_id)(DB_ENV *dbenv, pid_t *pid, db_threadid_t *tid));
</pre>
<hr size=1 noshade>
Description: DB_ENV-&gt;set_thread_id
Declare a function that returns a unique identifier pair for the current
thread of control. The DB_ENV-&gt;set_thread_id method supports the
<a href="../../db4-devel-4.7.25/api_c/env_failchk.html">DB_ENV-&gt;failchk</a> method. For more information, see
<a href="../../db4-devel-4.7.25/ref/cam/app.html">Architecting Data Store and Concurrent
Data Store applications</a>, and <a href="../../db4-devel-4.7.25/ref/transapp/app.html">Architecting Transactional Data Store applications</a>.
The DB_ENV-&gt;set_thread_id method configures operations performed using the specified
<a href="../../db4-devel-4.7.25/api_c/env_class.html">DB_ENV</a> handle, not all operations performed on the underlying
database environment.
The DB_ENV-&gt;set_thread_id method may be called at any time during the life of the
application.
The DB_ENV-&gt;set_thread_id method
returns a non-zero error value on failure
and 0 on success.

Parameters 
 thread_id<ul compact><li>The thread_id parameter is a function which returns a unique
identifier pair for a thread of control in a Berkeley DB application. The
function takes three arguments:</ul>
 
dbenv<ul compact><li>The dbenv parameter is the enclosing database environment
handle, allowing application access to the application-private fields
of that object.</ul>
pid<ul compact><li>The pid points to a memory location of type pid_t. The
process ID of the current thread of control may be returned in
this memory location.</ul>
tid<ul compact><li>The tid points to a memory location of type db_threadid_t. The
thread ID of the current thread of control may be returned in this
memory location.</ul>
 
 
The standard system library calls to return process and thread IDs are
often sufficient for this purpose (for example, getpid() and
pthread_self() on POSIX systems or GetCurrentThreadID on Windows
systems). However, if the Berkeley DB application dynamically creates
processes or threads, some care may be necessary in assigning unique
IDs. In most threading systems, process and thread IDs are available
for re-use as soon as the process or thread exits. If a new process or
thread is created between the time of process or thread exit, and the
<a href="../../db4-devel-4.7.25/api_c/env_failchk.html">DB_ENV-&gt;failchk</a> method is run, it may be possible for
<a href="../../db4-devel-4.7.25/api_c/env_failchk.html">DB_ENV-&gt;failchk</a> to not detect that a thread of control exited
without properly releasing all Berkeley DB resources.
It may be possible to handle this problem by inhibiting process or
thread creation between thread of control exit and calling
<a href="../../db4-devel-4.7.25/api_c/env_failchk.html">DB_ENV-&gt;failchk</a>. Alternatively, the thread_id function
must be constructed to not re-use pid/tid pairs. For
example, in a single process application, the returned process ID might
be used as an incremental counter, with the returned thread ID set to
the actual thread ID. Obviously, the is_alive function
specified to the <a href="../../db4-devel-4.7.25/api_c/env_set_isalive.html">DB_ENV-&gt;set_isalive</a> method must be compatible with any
thread_id function specified to DB_ENV-&gt;set_thread_id.
The db_threadid_t type is configured to be the same type as a standard
thread identifier, in Berkeley DB configurations where this type is known (for
example, systems supporting pthread_t or thread_t, or DWORD on Windows).
If the Berkeley DB configuration process is unable to determine the type of a
standard thread identifier, the db_thread_t type is set to uintmax_t (or
the largest available unsigned integral type, on systems lacking the
uintmax_t type). Applications running on systems lacking a detectable
standard thread type, and which are also using thread APIs where a
thread identifier is not an integral value and so will not fit into the
configured db_threadid_t type, must either translate between the
db_threadid_t type and the thread identifier (mapping the thread
identifier to a unique identifier of the appropriate size), or modify
the Berkeley DB sources to use an appropriate db_threadid_t type. Note: we
do not currently know of any systems where this is necessary. If your
application has to solve this problem, please contact our support group
and let us know.
If no thread_id function is specified by the application, the
Berkeley DB library will identify threads of control by using the taskIdSelf()
call on VxWorks, the getpid() and GetCurrentThreadID() calls on Windows,
the getpid() and pthread_self() calls when the Berkeley DB library has been
configured for POSIX pthreads or Solaris LWP threads, the getpid() and
thr_self() calls when the Berkeley DB library has been configured for UI
threads, and otherwise getpid().
 Errors
The DB_ENV-&gt;set_thread_id method
may fail and return one of the following non-zero errors:
 
EINVAL<ul compact><li>An
invalid flag value or parameter was specified.</ul>
 
<hr size=1 noshade>
 Class
<a href="../../db4-devel-4.7.25/api_c/env_class.html">DB_ENV</a>
 See Also
<a href="../../db4-devel-4.7.25/api_c/env_list.html">Database Environments and Related Methods</a>
</tt>
<table width="100%"><tr><td> </td><td align=right>
<a href="../../db4-devel-4.7.25/api_c/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