Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 144 invoked from network); 7 Apr 2005 11:02:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Apr 2005 11:02:40 -0000 Received: (qmail 80037 invoked by uid 500); 7 Apr 2005 11:02:38 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 79987 invoked by uid 500); 7 Apr 2005 11:02:38 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 79973 invoked by uid 99); 7 Apr 2005 11:02:38 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from brmea-mail-4.Sun.COM (HELO brmea-mail-4.sun.com) (192.18.98.36) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 07 Apr 2005 04:02:36 -0700 Received: from phys-mpk-1 ([129.146.11.81]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j37B2ZK2013574 for ; Thu, 7 Apr 2005 05:02:35 -0600 (MDT) Received: from conversion-daemon.mpk-mail1.sfbay.sun.com by mpk-mail1.sfbay.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) id <0IEK00F01ORT2I@mpk-mail1.sfbay.sun.com> (original mail from David.Vancouvering@Sun.COM) for derby-dev@db.apache.org; Thu, 07 Apr 2005 04:02:35 -0700 (PDT) Received: from sun.com (vpn-129-150-117-209.UK.Sun.COM [129.150.117.209]) by mpk-mail1.sfbay.sun.com (iPlanet Messaging Server 5.2 HotFix 1.24 (built Dec 19 2003)) with ESMTP id <0IEK006XSPC9YG@mpk-mail1.sfbay.sun.com> for derby-dev@db.apache.org; Thu, 07 Apr 2005 04:02:34 -0700 (PDT) Date: Thu, 07 Apr 2005 12:02:58 +0100 From: David Van Couvering Subject: Re: more background threads In-reply-to: <4254BCEA.6010103@debrunners.com> To: Derby Development Message-id: <42551362.7090101@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 References: <424AA335.1090405@sun.com> <424C5BC6.10900@sbcglobal.net> <425445D4.1030003@sun.com> <42544BF0.4020307@debrunners.com> <42545FAB.4010707@sun.com> <4254BCEA.6010103@debrunners.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N So I suppose conceivably you could have multiple systems in a VM if you have multiple classloaders, each of which loads its own copy of the JDBC driver class... David Daniel John Debrunner wrote: > David Van Couvering wrote: > > >>OK... I'm still trying to get clear on your concepts and terms -- how >>is a "system" defined? I'm thinking "all of Derby" within a given VM? > > > Correct. A system corresponds to the loading of Derby's JDBC driver > within a JVM, a system can have multiple databases open within that JVM. > > > >>Before I spend a lot more time on this: are there other things that are >>reasonable in scale and scope you could really use my help on that are >>generally felt to be of higher priority? I don't need to spend a lot of >>time on this if it currently works pretty well and is not causing a lot >>of pain or problems... > > > Apart from fixing the issue of too many Java threads when a large number > of databases are active, I see the cleanup in this area as a step > towards supporting: > > - timed events - java.util.TimerTask integration, for setQueryTimeout > at least > > - Serviceable items that can be executed during idle time, e.g. > background data flushing, space reclaimation, background statistics > gathering, etc. > > While these items could be fitted into the current scheme, I think a > cleanup would make it easier. > > Dan. >