It is our great pleasure to announce the first release candidate for eXist 3.0.
As always, the purpose of this release candidate is to collect feedback on performance and compatibility. Whilst it is considered feature complete, we would not yet recommend it for production environments.
eXist 3.0.RC1 is the culmination of over 550 changes made in the last six months. The main focus has been on fixing bugs, migrating to Java 8 and improving the performance of eXist. The move to Java 8 alone has brought many internal improvements in eXist, enabling us to work with a leaner and safer code base; resulting in better resource and lock management, and improved performance for our users.
## Mission Critical Bug Fixes
There have been numerous bug fixes and enhancements since eXist 2.2, the most critical are:
- Patched a memory leak in the Java service wrapper that occurred on certain Linux systems
- Solved a potential deadlock which manifested when storing XQuery files into the database under certain conditions
- Fixed a memory leak when storing query results into the HTTP session; Web applications making use of the HTTP session should now consume less memory and scale further
- Fixed an occasional deadlock when shutting down the database
- Fixes to match highlighting with the Lucene full text index
- Lucene range index now correctly handles != comparisons
http://exist-db.org/xquery/text) XQuery module has also been removed. Users should now look toward
fn:analyze-string. There have been some small changes to some of the internal APIs. e.g. XQueryService has been moved from DBBroker to BrokerPool. * EXPath packages that incorporate Java libraries may no longer work with eXist 3.0 and may need to be recompiled for our API changes; packages should now explicitly specify the eXist versions that they are compatible with.
eXist-3.0.RC1 is available for download from No link definition found for id 2. The older Sourceforge download page is no longer updated. Maven artifacts for eXist-3.0.RC1 are available from our mvn-repo.