db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-594) Some rawStoreDaemon threads are not stopped
Date Wed, 06 Sep 2006 07:40:22 GMT
     [ http://issues.apache.org/jira/browse/DERBY-594?page=all ]

Knut Anders Hatlen updated DERBY-594:

    Assignee:     (was: Knut Anders Hatlen)

Unassigning the issue since I am not working on it.

> Some rawStoreDaemon threads are not stopped
> -------------------------------------------
>                 Key: DERBY-594
>                 URL: http://issues.apache.org/jira/browse/DERBY-594
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions:,
>         Environment: Solaris 10 x86, NetBSD 2.1 (x86), Sun JDK 1.4.2/1.5.0
>            Reporter: 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


View raw message