public class EnvironmentFailureException extends RunRecoveryException
Environmentas a whole. For failures that impact only the current operation and/or transaction, see
OperationFailureException). For an overview of all exceptions thrown by JE, see
Depending on the nature of the failure, this exception may indicate that
Environment.close() must be called. The application should catch
EnvironmentFailureException and then call
false is returned, all
handles (instances) must be closed and re-opened in order to run recovery
and continue operating. If
true is returned, the
Environment can continue operating without being closed and re-opened.
Also note that
Environment.isValid() may be called at any time, not
just during exception handling.
The use of the
Environment.isValid() method allows JE to determine
dynamically whether the failure requires recovery or not, and allows for
this determination to change in future releases. Over time, internal
improvements to error handling may allow more error conditions to be handled
without invalidating the
(Although this exception class extends
does not always indicate that recovery is necessary, as described above.
RunRecoveryException has been deprecated and
EnvironmentFailureException should be used instead.)
EnvironmentFailureException consistently occurs soon after
opening the Environment, this may indicate a persistent problem. It may
indicate a system problem or a persistent storage problem. In this case,
human intervention is normally required and restoring from a backup may be
Note that subclasses of
EnvironmentFailureException indicate how
to handle the exception in more specific ways.
Thread.interruptis called for a thread performing JE operations, a
ThreadInterruptedExceptionis thrown. Since interrupting a thread is intentional, it does not indicate a persistent problem and human intervention is not normally required.
IOExceptionoccurs while writing to the JE log, a
LogWriteExceptionis thrown. Although an
IOExceptioncan occur for different reasons, it is a hint that the disk may be full and applications may wish to attempt recovery after making more disk space available.
com.sleepycat.je.reppackage for more information. Such exceptions may require special handling.
Environment.close() is not called after an
EnvironmentFailureException invalidates the
subsequent method calls for the
Environment will throw the same
exception. This provides more than one opportunity to catch and handle the
specific exception subclass that caused the failure.
|Modifier and Type||Method and Description|
Whether the EnvironmentFailureException indicates that the log is corrupt, meaning that a network restore (or restore from backup) should be performed.
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
public boolean isCorrupted()
This method currently returns true only when corruption has been
detected and is persistent. This may have been detected by verifying
checksums in the disk data log, and in this case the corruption
indicates a media/disk failure. The checksum error may have
been detected when accessing data normally via the JE API, or by the
background data verifier (see
Or a persistent Btree corruption may have been detected by the data
EnvironmentConfig.VERIFY_BTREE) or by the
Environment.verify(VerifyConfig, PrintStream) or
Database.verify(VerifyConfig) methods. This method will
returns true in all such cases.
Additionally, when a persistent corruption is detected and the Environment is open for read-write access, a marker file named 7fffffff.jdb is created in the Environment directory that will prevent re-opening the environment. If an attempt is made to re-open the Environment, the original EnvironmentFailureException will be thrown. This is meant to safeguard against using a corrupt environment when the original exception is accidentally overlooked. While the marker file can be deleted to allow re-opening the environment, this is normally unsafe and is not recommended.
Copyright (c) 2002, 2017 Oracle and/or its affiliates. All rights reserved.