Today we have put a maintenance release of our stable 7.4 version online.

Here are the three most important changes that we made by porting back code from our development release:
(1) We now distribute ObjectManager Enterprise (OME) along with our stable distribution also. If you are a 7.4
user you can now use this tool to browse and modify database files. OME comes as an Eclipse plugin for
Java and as a Visual Studio plugin for .NET. OME needs to be installed separately from:
- /db4o-7.4/ome (Java)
- /db4o-7.4/omn2008 (.NET: Visual Studio 2008)
- /db4o-7.4/omn2005 (.NET: Visual Studio 2005)

(2) A Configuration object can no longer be reused to open multiple ObjectContainers. Please always call Db4o.newConfiguration() (Java) / Db4oFactory.NewConfiguration() (.NET) to create a new Configuration object for each ObjectContainer / ObjectServer that you want to open. This change was necessary because we became aware that shared configuration state could lead to unwanted locking issues. Reusing a Configuration for a second open call will now throw an exception. We recommend only to use the openFile()/openServer() calls that require a Configuration object as one of the parameters. This way you can make sure that you are explicit about which Configuration you use.

(3) In Client/Server mode each client now maintains it's own ReferenceSystem on the server side, should there be the need to activate objects to execute unoptimized queries. This way we can guarantee better isolation by executing queries against uncommitted state.

Here is a list of important Jira issues that have been marked as fixed for the 7.4 branch since the previous 7.4 release:
COR-1814 - Configuration reuse produces deadlock
COR-1813 - Inconsistency in the reference systems if the server ObjectContainer is accessed via networking and embedded clients
COR-1806 - Removing from ReferenceSystem by ID does not check ObjectReference identity
COR-1725 - BLOAT cache fills up the heap
COR-1597 - db4o_osgi with rcp app problem
COR-1596 - Allow to specify dedicated target storage for backup
COR-1582 - Activating a map to depth 1 prevents it from being activated to depth 2
COR-1558 - db4o should throw when a configuration is reused
COR-1809 - Potential memory leak in ClientTransactionPool
COR-1598 - Diagnostics warns about missing field indexes on class-only queries
COR-1599 - Synchronize KnownClassesRepository access in GenericReflector against database lock

Enjoy the new release!
Your db4o team.