[jira] [Closed] (DERBY-594) Some rawStoreDaemon threads are not stopped

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen closed DERBY-594.
------------------------------------
    Resolution: Cannot Reproduce

I revived store/encryptDatabase.sql (it has been converted to JUnit after this issue was filed) and tried to reproduce the problem. I could only see one rawStoreDaemon thread with jstack at the end of the test (which is expected, since one database is booted). I even tried with 10.2.1.6, which the bug was originally filed against, but didn't see any extra threads.

Since I don't remember how to reproduce the problem, if there actually is one, and since no one else seems to have tripped across it, I'm closing the bug as Cannot Reproduce.

> Some rawStoreDaemon threads are not stopped
> -------------------------------------------
>
>                 Key: DERBY-594
>                 URL: https://issues.apache.org/jira/browse/DERBY-594
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions: 10.1.2.1, 10.2.1.6
>         Environment: Solaris 10 x86, NetBSD 2.1 (x86), Sun JDK 1.4.2/1.5.0
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
>              Labels: derby_triage10_5_2
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)