JE 3.2.65 contains an important bug fix having to do with Two Phase Commit processing, as reported in this OTN Forum posting. Specifically, if a transaction is prepared, but not committed, it is possible over the course of multiple recovery invocations (re-opening the JE environment) to have the transaction disappear (thereby preventing it from ever being committed). If you're using distributed Two Phase Commit transactions, you'll want to pick up this release when it's available.
« Berkeley DB Java Edition and Remote File Systems | Main | Berkeley DB Java Edition and Scala »
Berkeley DB Java Edition Two Phase Commit Bug Fix
Search All Blogs
Google Search
About This Entry
This page contains a single entry from the blog posted on November 21, 2007 11:22 AM.
The previous post in this blog was Berkeley DB Java Edition and Remote File Systems.
The next post in this blog is Berkeley DB Java Edition and Scala.
Many more can be found on the main index page or by looking through the archives.
