db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-594) Some rawStoreDaemon threads are not stopped
Date Thu, 02 Jul 2009 23:11:48 GMT

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

Mike Matrigali updated DERBY-594:
---------------------------------

    Urgency: Normal

Triaged July 2, 2009:  assigned normal urgency.

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message