+1 I think that is an important issue to resolve; my application is also affected by this.
-geoff “XML? Too much like HTML. It'll never work on the Web!” -anonymous ________________________________ From: Arnaud Masson <[email protected]> To: Derby Discussion <[email protected]> Sent: Monday, May 4, 2009 2:15:50 AM Subject: Re: Many background threads (rawStoreDaemon) Knut Anders Hatlen a écrit : > [email protected] (Dag H. Wanvik) writes: > > >> Arnaud Masson <[email protected]> writes: >> >> >>> I have an application that opens several small derby databases (using >>> EmbeddedDriver). >>> Most of of these instances don't handle many requests. >>> The problem is that each instance maintain its own thread >>> "derby.rawStoreDaemon". >>> Is there a way to use a thread pool shared between instances instead ? >>> (There is also a discussion about that here: >>> http://osdir.com/ml/apache.db.derby.devel/2005-04/msg00093.html) >>> >> I am not aware any progress has been made on this issue, unfortunately. >> > > If you think it should be adressed, filing a JIRA issue is a good first > step: https://issues.apache.org/jira/browse/DERBY > > (I don't think there is one filed yet, is it?) > > No I didn't find a Jira entry for that. I have entered https://issues.apache.org/jira/browse/DERBY-4210. Thanks!
