# Berkeley DB Java Edition
Release Notes

3.2.13, December 06, 2006

## Overview

Berkeley DB Java Edition (JE) is a 100% pure Java implementation of Berkeley DB. It implements a transactional store model based on a B+Tree access method.

The documentation set for JE includes:

- JE's capabilities and features are described in the Getting Started with Berkeley DB Java Edition guide. That document also introduces the JE API set.
- For a description of how to use JE and the new Direct Persistence Layer, see the Getting Started with the Direct Persistence Layer guide.
- For a description of how to use JE and the Berkeley DB Java Collections API, see the collections tutorial.
- For an overview on using transactions, see Writing Transactional Applications with Berkeley DB, Java Edition
- For a complete description of the JE API set, see the Javadoc.

This is release 3.2.13 of Berkeley DB Java Edition, and the first release in the JE 3.2 line. The changes introduced in 3.2.13 mainly encompass bug fixes and efficiency improvements, but also include a forward-compatible file format change.

Key changes since version JE 3.1.0 are summarized below; the complete list of changes can also be found in the change log page.

Note: If you are using Mac OS X, please be aware of the following issue. Java version 1.4.2 on Mac OS X reports the wrong value for Runtime.maxMemory. JE calculates the default cache size as a percentage of maxMemory. Because of this, for Java 1.4.2 on Mac OS X only, JE will assume that the Java maxMemory value is 64 MB. With the default je.maxMemoryPercent configuration parameter (60%) the default JE cache size will be approximately 38 MB. This default is fixed -- it does not change if the Java memory size is different than 64 MB. To specify a different JE cache size, you must explicitly set the je.maxMemory configuration property. The je.maxMemory property can be specified in the je.properties file or by calling EnvironmentConfig.setCacheSize.

### Log File On-Disk Format Changes:

JE 3.2.13 has moved to on-disk file format 5.

The change is forward compatible in that JE files created with release 3.1.0 and earlier can be read when opened with JE 3.2.13. The change is not backward compatible in that files created with JE 3.2.13 cannot be read by earlier releases. Note that if an existing environment is opened read/write, a new log file is written by JE 3.2.13 and the environment can no longer be read by earlier releases.[#15195]

### Other Changes:

JE 3.2.13 includes

- New configuration properties to control background I/O.
- Tuple binding support and DPL support for BigInteger.
- A variety of bug fixes and documentation enhancements.

See the change log for the complete and detailed description of all changes.

Copyright 1996,2006 Oracle. All rights reserved.