| Class and Description | 
|---|
| com.sleepycat.je.jmx.JEMBeanHelper As of JE 4, JEMBeanHelper is deprecated in favor of the concrete
 MBeans available by default with a JE environment. These MBeans can be 
 registered and enabled by the environment by setting the following JVM
 property:
     JEMonitor: 
         This MBean provides general stats monitoring and access to basic 
         environment level operations.
 JEMBeanHelper is a utility class for the MBean implementation which wants to
 add management of a JE environment to its capabilities. MBean
 implementations can contain a JEMBeanHelper instance to get MBean metadata
 for JE and to set attributes, get attributes, and invoke operations.
  com.sleepycat.je.jmx.JEMonitor and the example program jmx.JEApplicationMBean are two MBean implementations which provide support different application use cases. See those classes for examples of how to use JEMBeanHelper. | 
| com.sleepycat.je.LockStats as of 4.0.10, replaced by  Environment.getStats(StatsConfig). | 
| Exceptions and Description | 
|---|
| com.sleepycat.je.LockNotGrantedException replaced by  LockNotAvailableException | 
| com.sleepycat.je.rep.MasterReplicaTransitionException as of JE 5.0.88 because the environment no longer needs to
 restart when transitioning from master to replica. | 
| com.sleepycat.je.RunRecoveryException replaced by  EnvironmentFailureExceptionandEnvironment.isValid(). | 
| Field and Description | 
|---|
| com.sleepycat.je.EnvironmentConfig.CLEANER_ADJUST_UTILIZATION in JE 6.3. Adjustments are no longer needed because LN log
 sizes have been stored in the Btree since JE 6.0. | 
| com.sleepycat.je.EnvironmentConfig.CLEANER_BACKGROUND_PROACTIVE_MIGRATION This parameter is ignored and proactive migration is no
 longer supported due to its negative impact on eviction and
 checkpointing. To reduce a cleaner backlog, configure more cleaner
 threads. | 
| com.sleepycat.je.EnvironmentConfig.CLEANER_FOREGROUND_PROACTIVE_MIGRATION This parameter is ignored and proactive migration is no
 longer supported due to its negative impact on eviction and Btree
 splits. To reduce a cleaner backlog, configure more cleaner threads. | 
| com.sleepycat.je.EnvironmentConfig.CLEANER_LAZY_MIGRATION This parameter is ignored and lazy migration is no longer
 supported due to its negative impact on eviction and checkpointing.
 To reduce a cleaner backlog, configure more cleaner threads. | 
| com.sleepycat.je.EnvironmentConfig.CLEANER_MAX_BATCH_FILES in 7.0. No longer used because the cleaner no longer has a
 backlog. | 
| com.sleepycat.je.EnvironmentConfig.COMPRESSOR_PURGE_ROOT as of 3.3.87.  Compression of the root node no longer has
 any benefit and this feature has been removed.  This parameter has no
 effect. | 
| com.sleepycat.je.EnvironmentConfig.EVICTOR_DEADLOCK_RETRY as of JE 4.1, since the single evictor thread has
 been replaced be a more robust thread pool. | 
| com.sleepycat.je.EnvironmentConfig.EVICTOR_LRU_ONLY as of JE 6.0. This parameter is ignored by the new,
 more efficient and more accurate evictor. | 
| com.sleepycat.je.EnvironmentConfig.EVICTOR_NODES_PER_SCAN as of JE 6.0. This parameter is ignored by the new, more
 efficient and more accurate evictor. | 
| com.sleepycat.je.rep.ReplicationConfig.HELPER_HOSTS replaced by  ReplicationMutableConfig.HELPER_HOSTS. | 
| com.sleepycat.je.EnvironmentConfig.LOCK_OLD_LOCK_EXCEPTIONS since JE 6.5; has no effect, as if it were set to false. | 
| com.sleepycat.je.EnvironmentConfig.LOG_CHUNKED_NIO NIO is no longer used by JE and this parameter has no
 effect. | 
| com.sleepycat.je.EnvironmentConfig.LOG_DIRECT_NIO NIO is no longer used by JE and this parameter has no
 effect. | 
| com.sleepycat.je.rep.ReplicationMutableConfig.LOG_FLUSH_TASK_INTERVAL as of 7.2. Replaced by  EnvironmentConfig.LOG_FLUSH_SYNC_INTERVAL. For compatibility with
 earlier releases, if this parameter is specified its value will be used
 as the flush sync interval; in this case,EnvironmentConfig.LOG_FLUSH_SYNC_INTERVALmay not also be specified. | 
| com.sleepycat.je.EnvironmentConfig.LOG_N_DATA_DIRECTORIES as of 7.3. This feature is not known to provide benefits
 beyond that of a simple RAID configuration, and will be removed in the
 next release, which is slated for mid-April, 2017. | 
| com.sleepycat.je.EnvironmentConfig.LOG_USE_NIO NIO is no longer used by JE and this parameter has no
 effect. | 
| com.sleepycat.je.EnvironmentConfig.NODE_DUP_TREE_MAX_ENTRIES this property no longer has any effect;  DatabaseConfig.setNodeMaxEntries(int)should be used instead. | 
| com.sleepycat.je.Durability.READ_ONLY_TXN use  TransactionConfig.setReadOnly(boolean)instead. | 
| com.sleepycat.je.rep.ReplicationConfig.REP_STREAM_TIMEOUT and no longer used as of JE 7.5. Reserved files are now
 retained based on available disk space -- see
  EnvironmentConfig.MAX_DISKandEnvironmentConfig.FREE_DISKshould be used instead.
 However, this param is still used when some, but not all, nodes in a
 group have been upgraded to 7.5 or later. | 
| com.sleepycat.je.rep.ReplicationConfig.REPLAY_COST_PERCENT and no longer used as of JE 7.5. Reserved files are now
 retained based on available disk space -- see
  EnvironmentConfig.MAX_DISKandEnvironmentConfig.FREE_DISKshould be used instead. | 
| com.sleepycat.je.rep.ReplicationConfig.REPLAY_DB_HANDLE_TIMEOUT replaced by  ReplicationMutableConfig.REPLAY_DB_HANDLE_TIMEOUT. | 
| com.sleepycat.je.rep.ReplicationConfig.REPLAY_FREE_DISK_PERCENT and no longer needed as of JE 7.5. Reserved files are now
 retained based on available disk space -- see
  EnvironmentConfig.MAX_DISKandEnvironmentConfig.FREE_DISKshould be used instead.
 However, this param is still used when it has been specified and
 is non-zero, and FREE_DISK has not been specified. In this case,
 REPLAY_FREE_DISK_PERCENT overrides the FREE_DISK default value. If
 both REPLAY_FREE_DISK_PERCENT and FREE_DISK are specified, an
 IllegalArgumentException is thrown. | 
| com.sleepycat.je.rep.ReplicationConfig.REPLAY_MAX_OPEN_DB_HANDLES replaced by  ReplicationMutableConfig.REPLAY_MAX_OPEN_DB_HANDLES. | 
| com.sleepycat.je.rep.ReplicationMutableConfig.RUN_LOG_FLUSH_TASK as of 7.2. Log flushing can be disabled by setting  EnvironmentConfig.LOG_FLUSH_SYNC_INTERVALandEnvironmentConfig.LOG_FLUSH_NO_SYNC_INTERVALto zero. For compatibility
 with earlier releases, if this parameter is specified as false, no log
 flushing will be performed; in this case,EnvironmentConfig.LOG_FLUSH_SYNC_INTERVALandEnvironmentConfig.LOG_FLUSH_NO_SYNC_INTERVALmay not also be specified. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_CONSOLE in favor of  CONSOLE_LOGGING_LEVELAs of JE
 4.0, use the standard java.util.logging configuration
 methodologies. To enable console output, set
 com.sleepycat.je.util.ConsoleHandler.level = <LEVEL> through
 the java.util.logging configuration file, or through the
 java.util.logging.LogManager. To set the handler level programmatically,
 set "com.sleepycat.je.util.ConsoleHandler.level" in the
 EnvironmentConfig object. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_DB As of JE 4.0, event tracing to the .jdb files has been
 separated from the java.util.logging mechanism. This parameter has
 no effect. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_FILE in favor of  FILE_LOGGING_LEVELAs of JE 4.0,
 use the standard java.util.logging configuration methodologies. To
 enable logging output to the je.info files, set
 com.sleepycat.je.util.FileHandler.level = <LEVEL> through the
 java.util.logging configuration file, or through the
 java.util.logging.LogManager. To set the handler level programmatically,
 set "com.sleepycat.je.util.FileHandler.level" in the EnvironmentConfig
 object. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_FILE_COUNT As of JE 4.0, use the standard java.util.logging
 configuration methodologies. To set the FileHandler output file count,
 set com.sleepycat.je.util.FileHandler.count = <NUMBER>
 through the java.util.logging configuration file, or through the
 java.util.logging.LogManager. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_FILE_LIMIT As of JE 4.0, use the standard java.util.logging
 configuration methodologies. To set the FileHandler output file size,
 set com.sleepycat.je.util.FileHandler.limit = <NUMBER>
 through the java.util.logging configuration file, or through the
 java.util.logging.LogManager. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_LEVEL As of JE 4.0, use the standard java.util.logging
 configuration methodologies. Set logging levels using class names
 through the java.util.logging configuration file, or through the
 java.util.logging.LogManager. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_LEVEL_CLEANER As of JE 4.0, use the standard java.util.logging
 configuration methodologies. To see cleaner logging, set
 com.sleepycat.je.cleaner.level = <LEVEL> through the
 java.util.logging configuration file, or through the
 java.util.logging.LogManager. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_LEVEL_EVICTOR As of JE 4.0, use the standard java.util.logging
 configuration methodologies. To see evictor logging, set
 com.sleepycat.je.evictor.level = <LEVEL> through the
 java.util.logging configuration file, or through the
 java.util.logging.LogManager. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_LEVEL_LOCK_MANAGER As of JE 4.0, use the standard java.util.logging
 configuration methodologies. To see locking logging, set
 com.sleepycat.je.txn.level = <LEVEL> through the
 java.util.logging configuration file, or through the
 java.util.logging.LogManager. | 
| com.sleepycat.je.EnvironmentConfig.TRACE_LEVEL_RECOVERY As of JE 4.0, use the standard java.util.logging
 configuration methodologies. To see recovery logging, set
 com.sleepycat.je.recovery.level = <LEVEL> through the
 java.util.logging configuration file, or through the
 java.util.logging.LogManager. | 
| com.sleepycat.je.EnvironmentConfig.TREE_MAX_DELTA as of JE 6.0.  The  EnvironmentConfig.TREE_BIN_DELTAparam alone now
 determines whether a delta is logged. | 
| Constructor and Description | 
|---|
| com.sleepycat.je.util.DbDump(Environment, String, PrintStream, String, boolean) Please use the 4-arg ctor without outputDirectory instead. | 
| com.sleepycat.je.util.DbVerify(Environment, String, boolean) as of 7.5, use  Environment.verify(com.sleepycat.je.VerifyConfig, java.io.PrintStream)orDatabase.verify(com.sleepycat.je.VerifyConfig)instead. These methods allow
 specifying allVerifyConfigproperties. | 
| com.sleepycat.je.rep.monitor.Monitor(ReplicationConfig) As of JE 5, replaced by
  Monitor.Monitor(MonitorConfig) | 
| Enum Constant and Description | 
|---|
| com.sleepycat.je.CacheMode.KEEP_HOT please use  CacheMode.DEFAULTinstead. As of JE 4.0, this mode
 functions exactly as ifCacheMode.DEFAULTwere specified. | 
| com.sleepycat.je.CacheMode.MAKE_COLD please use  CacheMode.UNCHANGEDinstead. As of JE 4.0, this
 mode functions exactly as ifCacheMode.UNCHANGEDwere specified. | 
Copyright (c) 2002, 2017 Oracle and/or its affiliates. All rights reserved.