You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by culgr01 <gr...@ca.com> on 2015/12/01 19:53:47 UTC
What creates rawStoreDaemon threads in embedded derby db?
(Developers)
Hi all,
Sorry, for cross posting this, but I was getting nothing in the user group.
Also, it is really more of a developer question.
The code I am working on creates embedded derby connections in an
implementation of PoolableObjectFactory.
conn = DriverManager.getConnection(jdbcProtocol+"database/CacheDB;", user,
password);
The connections are "destroyed" in destroyObject just by calling .close().
It seems to work fine, normally. However, someone else running the program
got several thousand rawStoreDaemon threads.
I can't recreate these extra threads. What's worse I can't even seem to make
more than one derby.rawStoreDaemon threads. I have had up to 100 active
connections and several users at once, but nothing seems to even make a
second derby.rawStoreDaemon thread.
My basic question is, what makes these threads? How come there is ever more
than one?
Also, is there some safe way kill these threads?
Thanks,
GC
--
View this message in context: http://apache-database.10148.n7.nabble.com/What-creates-rawStoreDaemon-threads-in-embedded-derby-db-Developers-tp145106.html
Sent from the Apache Derby Developers mailing list archive at Nabble.com.