[ http://issues.apache.org/jira/browse/DERBY-2083?page=all ]
Daniel John Debrunner updated DERBY-2083:
-----------------------------------------
Attachment: d2083_store_shutdown_diff.txt
Patch so that the store calls shutdown() on its StorageFactory. Is only a
partial solution as the shutdown() method for all StorageFactory
implementations is empty but is required as part of the api and will take
effect once the StorageFactory shutdown method for database in a jar closes its
ZipFile.
I believe the bug that changes the error message when closing the zip is
addedis in the monitor. I'll be addressing that with a separate patch.
> Shutting down a database loaded from a jar leaves an open file reference to
> the jar file containing the database.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2083
> URL: http://issues.apache.org/jira/browse/DERBY-2083
> Project: Derby
> Issue Type: Bug
> Components: Store, Services
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Assigned To: Daniel John Debrunner
> Priority: Minor
> Attachments: d2083_store_shutdown_diff.txt
>
>
> The shutdown() method of JarStorageFactory probably needs to close the
> zipData file but adding that code changes the behaviour of shutting down such
> a database to report database not found instead of database shutdown.
> Even with the above method changed and the problem fixed there may be a store
> error in that I couldn't see any store code that calls
> StorageFactory.shutdown() for the data segement, in this case the database is
> read only since it is from a jar.
> Seen in some new test cases being added to DatabaseClassLoadingTest (in the
> conversion from dcl.sql)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
