[DERBY-594] Some rawStoreDaemon threads are not stopped

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 10.1.2.1, 10.2.1.6
• Component/s: Services
• Labels: derby_triage10_5_2
• Environment: Solaris 10 x86, NetBSD 2.1 (x86), Sun JDK 1.4.2/1.5.0
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Knut Anders Hatlen
• Created: 01/Oct/05 19:21
• Updated: 19/Sep/14 13:06
• Resolved: 19/Sep/14 13:06

Description

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.