Berkeley DB: DbTxnMgr::close
Google

ee,hash,hashing,transaction,transactions,locking,logging,access method,access me thods,java,C,C++">

DbTxnMgr::close


#include <db_cxx.h>

int DbTxnMgr::close();

Description

The DbTxnMgr::close method detaches a process from the transaction environment specified by the DbTxnMgr object. All mapped regions are unmapped and any allocated resources are freed. Any uncommitted transactions are aborted.

In addition, if the dir argument to DbTxnMgr::open was NULL and dbenv was not initialized using DbEnv::appinit, all files created for this shared region will be removed, as if the DbTxnMgr::unlink method were called.

In multi-threaded applications, only a single thread may call the DbTxnMgr::close method.

The DbTxnMgr::close method either returns errno or throws an exception that encapsulates an errno on failure, and 0 on success.

Errors

If a fatal error occurs in Berkeley DB, the DbTxnMgr::close method may fail and either return DB_RUNRECOVERY or throw an exception encapsulating DB_RUNRECOVERY, at which point all subsequent database calls will also fail in the same way. Methods marked as returning errno will, by default, throw an exception that encapsulates the error information. The default error behavior can be changed, see DbException.

The DbTxnMgr::close method may fail and throw an exception for any of the errors specified for the following Berkeley DB and C library functions: abort(3), close(3), fcntl(3), fflush(3), fprintf(3), free(3), getpid(3), DbLockTab::vec, DbLog::flush, memset(3), munmap(3), shmctl(3), shmdt(3), strerror(3), strlen(3), DbTxn::abort, unlink(3), vfprintf(3), and vsnprintf(3).

Class

DbTxnMgr

See Also

DbTxnMgr::begin, DbTxnMgr::checkpoint, DbTxnMgr::close, DbTxnMgr::open, DbTxnMgr::stat and DbTxnMgr::unlink.