All releases of Berkeley DB Java Edition
Release Notes: A bug that could cause an EnvironmentFailureException with LOG_FILE_NOT_FOUND during recovery was fixed. A bug that prevents using a DPL class converter mutation for a proxy class was fixed. A bug that caused a hard deadlock when attempting to abort a transaction in one thread, while performing operations using the transaction in another thread was fixed. Now, rather than a hard deadlock, an IllegalStateException will be thrown in this circumstance.
Release Notes: The 4.1 version series delivers up to three times better performance than 4.0 in some read-only scenarios where the working set doesn't fit in the cache. This release includes multi-threaded cache management and advanced in-memory Internal Node compression.
Release Notes: This release fixes a problem that could cause LogFileNotFoundException in large databases. This could cause data loss, so all users are strongly recommended to upgrade. This problem is found in all prior releases. The bug can occur only for databases with a Btree that is 4 or more levels deep. For the default maximum entries per Btree node (128), this means the database must have grown to at least 10 million records to be a candidate for occurrence of this problem. This is only an approximation, and may be larger or smaller if DatabaseConfig.setNodeMaxEntries has been called.
Release Notes: Direct Persistence Layer (DPL) is an EJB-style API using Java annotations to dramatically reduce development time, ease schema design, and provide indexed access to objects improving data access times. Schema Evolution of DPL Classes: POJO data contained in Berkeley DB Java Edition using the DPL can now evolve gracefully from version to version.
Release Notes: Support for JTA, JCA, and JMX. Cleaner enhancements improve out of cache performance. The ability to manage data sets much larger than than the cache is vastly improved in this release. Sequences are now supported. The ability to relax the 'I' (isolation) in 'ACID' transactions is provided by adding support for read committed (sometimes called degree 2) isolation. This complements the existing ability to relax the 'D' (durability) constraints in favor of speed. These are design trade-offs left to the developer.
Release Notes: In addition to a number of bugfixes, a change was made to internal latching, which resulted in significant performance improvements in multi-threaded applications.
Release Notes: A great deal of speed and scalability enhancements were made.
Release Notes: This is the first general availability release of Berkeley DB Java Edition.
Release Notes: A number of bugfixes and speed enhancements were made.
No changes have been submitted for this release.
