Memory leak when attempting to boot non-existing database with the in-memory
back end
-------------------------------------------------------------------------------------
Key: DERBY-4432
URL: https://issues.apache.org/jira/browse/DERBY-4432
Project: Derby
Issue Type: Bug
Components: Store
Affects Versions: 10.5.3.0, 10.6.0.0
Environment: In-memory back end and large amount of boot attempts of
non-existing databases.
Reporter: Kristian Waagan
Assignee: Kristian Waagan
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").
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
