head 1.4; access; symbols RPM_4_2_1:1.1.1.1 RPM_4_2:1.1.1.1 RPM_4_1_1:1.1.1.1 RPM_4_0_5:1.1.1.1 RPM:1.1.1; locks; strict; comment @# @; 1.4 date 2008.01.02.09.54.00; author rse; state dead; branches; next 1.3; commitid z4cpSiAhOCXk5PLs; 1.3 date 2003.08.24.12.43.14; author rse; state Exp; branches; next 1.2; 1.2 date 2003.08.24.12.33.49; author rse; state dead; branches; next 1.1; 1.1 date 2002.09.19.20.34.05; author rse; state Exp; branches 1.1.1.1; next ; 1.1.1.1 date 2002.09.19.20.34.05; author rse; state Exp; branches; next ; desc @@ 1.4 log @remove the ancient RPM 4.2.1 source tree copy @ text @
DbMemoryException |
![]() ![]() |
import com.sleepycat.db.*;public class DbMemoryException extends DbException { public Dbt get_dbt(); }
This manual page describes the DbMemoryException class and how it is used by the various Db* classes.
A DbMemoryException is thrown when there is insufficient memory to complete an operation, and there is the possibility of recovering. An example is during a Db.get or Dbc.get operation with the Dbt flags set to Db.DB_DBT_USERMEM.
In a Java Virtual Machine, there are usually separate heaps for memory allocated by native code and for objects allocated in Java code. If the Java heap is exhausted, the JVM will throw an OutOfMemoryError, so you may see that exception rather than DbMemoryException.
The get_dbt method returns the Dbt that has insufficient memory to complete the operation, causing the DbMemoryException to be thrown.
![]() ![]() |
Copyright Sleepycat Software @ 1.3 log @Resolve: RPM 4.1 -> RPM 4.1.1 @ text @@ 1.2 log @Resolve: RPM 4.0.5 -> RPM 4.1 @ text @@ 1.1 log @Initial revision @ text @@ 1.1.1.1 log @Import: RPM 4.0.5 @ text @@