[ http://issues.apache.org/jira/browse/DERBY-594?page=comments#action_12368363 ]
Daniel John Debrunner commented on DERBY-594:
---------------------------------------------
Confirmed that this is not an issue for DERBY-538, the raw store daemon thread stops correctly
in the situation I'm seeing.
> Some rawStoreDaemon threads are not stopped
> -------------------------------------------
>
> Key: DERBY-594
> URL: http://issues.apache.org/jira/browse/DERBY-594
> Project: Derby
> Type: Bug
> Components: Services
> Versions: 10.1.2.0, 10.2.0.0
> Environment: Solaris 10 x86, NetBSD 2.1 (x86), Sun JDK 1.4.2/1.5.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Priority: Minor
>
> In some cases, loading a database will create a rawStoreDaemon thread
> which will run forever, even after Derby is shut down with
> DriverManager.getConnection("jdbc:derby:;shutdown=true").
> I have found two tests in derbyall (there are probably more) where
> threads are left running:
> - in store/rollForwardBackup.sql two threads are never terminated
> - in store/encryptDatabase.sql five threads are never terminated
> All the threads are named "derby.rawStoreDaemon" and created in
> org.apache.derby.impl.store.raw.RawStore.boot().
> It seems like this happens in some (but not all) cases where the
> loading of a database fails, but I am not able to say exactly what
> triggers this bug yet.
--
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
|