[DERBY-4432] Memory leak when attempting to boot non-existing database with the in-memory back end

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.5.3.0, 10.6.1.0
• Fix Version/s: 10.5.3.1, 10.6.1.0
• Component/s: Store
• Environment: In-memory back end and large amount of boot attempts of non-existing databases.
• Issue & fix info: Release Note Needed
• Assignee: Kristian Waagan
• Reporter: Kristian Waagan
• Created: 03/Nov/09 09:39
• Updated: 26/Jan/10 07:17
• Resolved: 12/Nov/09 08:34

Description

When attempting to boot a non-existing database with the in-memory back end, a DataStore is created and referenced by a map. Since the database doesn't exist, Derby won't use the DataStore again and it will hang around indefinitely in VFMemoryStorageFactory (or until the same database is actually created, in which case the data store will be used).

FYI, storage factory instances are instantiated liberally, including for the same service (i.e. six instances of VFMemoryStorageFactory may be created to boot "jdbc:derby:memory:myDB").

Issue Links

• is related to: DERBY-4428 Add proper delete mechanism for in-memory databases