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? -- View this message in context: http://apache-database.10148.n7.nabble.com/What-creates-rawStoreDaemon-threads-in-embedded-derby-db-tp145096.html Sent from the Apache Derby Users mailing list archive at Nabble.com.
