From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- .../db/ReplicationHandleDeadException.html | 417 +++++++++++---------- 1 file changed, 211 insertions(+), 206 deletions(-) (limited to 'docs/java/com/sleepycat/db/ReplicationHandleDeadException.html') diff --git a/docs/java/com/sleepycat/db/ReplicationHandleDeadException.html b/docs/java/com/sleepycat/db/ReplicationHandleDeadException.html index 114bd8c3..c3dc4f5d 100644 --- a/docs/java/com/sleepycat/db/ReplicationHandleDeadException.html +++ b/docs/java/com/sleepycat/db/ReplicationHandleDeadException.html @@ -1,228 +1,233 @@ - - - - - -ReplicationHandleDeadException (Oracle - Berkeley DB Java API) - - - - - - - - - - - - -
- - +//--> + + - - - - - - - - - - - - - - - - -
-Berkeley DB
version 5.3.21
-
- + + +
+ + +
+ + + - -
-

- -com.sleepycat.db -
-Class ReplicationHandleDeadException

-
-java.lang.Object
-  extended by java.lang.Throwable
-      extended by java.lang.Exception
-          extended by com.sleepycat.db.DatabaseException
-              extended by com.sleepycat.db.ReplicationHandleDeadException
-
-
-
All Implemented Interfaces:
Serializable
-
-
-
-
public class ReplicationHandleDeadException
extends DatabaseException
- - -

-Thrown when a database handle has been invalidated because a replication +

+
com.sleepycat.db
+

Class ReplicationHandleDeadException

+
+
+ +
+
    +
  • +
    +
    All Implemented Interfaces:
    +
    java.io.Serializable
    +
    +
    +
    +
    public class ReplicationHandleDeadException
    +extends DatabaseException
    +
    Thrown when a database handle has been invalidated because a replication election unrolled a committed transaction. When this happens the handle is no longer able to be used and the application -must close the handle using the Database.close method and open a new +must close the handle using the Database.close method and open a new handle. This exception is thrown when a client unrolls a transaction in order to synchronize with a new master. If the application was permitted to use the original handle, it's possible the handle might attempt to access nonexistent -resources. -

    - -

    -

    -
    See Also:
    Serialized Form
    -
    - -

    - +resources.

    +
    See Also:
    Serialized Form
    +
  • +
+
+
+ +
+
-
- - - - - - - - - - - - - - - - - - -
-Berkeley DB
version 5.3.21
-
- + + +
+ + +
+ + + - -
-Copyright (c) 1996, 2012 Oracle and/or its affiliates. All rights reserved. - - +

Copyright (c) 1996, 2015 Oracle and/or its affiliates. All rights reserved.

+ + -- cgit v1.2.1