Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 49833 invoked from network); 5 Feb 2009 18:27:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Feb 2009 18:27:48 -0000 Received: (qmail 13720 invoked by uid 500); 5 Feb 2009 18:27:46 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 13701 invoked by uid 500); 5 Feb 2009 18:27:46 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 13692 invoked by uid 99); 5 Feb 2009 18:27:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Feb 2009 10:27:46 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [63.82.107.6] (HELO red.amberpoint.com) (63.82.107.6) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Feb 2009 18:27:39 +0000 Received: from [10.10.12.246] (knoppix.edgility.com [10.10.12.246] (may be forged)) by red.amberpoint.com (8.13.8/8.13.8) with ESMTP id n15IRHqU026939 for ; Thu, 5 Feb 2009 10:27:17 -0800 Message-ID: <498B2F85.4080900@amberpoint.com> Date: Thu, 05 Feb 2009 10:27:17 -0800 From: Bryan Pendleton User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: Derby Discussion Subject: Re: Too many open files References: <200902051919.54292.Johannes.Stamminger@astrium.eads.net> In-Reply-To: <200902051919.54292.Johannes.Stamminger@astrium.eads.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > On further investigation it seems to me that after closing an embedded derby > database some file handles (.dat, .lck and .log) are kept open (checked using > lsof). Closing a JDBC connection is not the same as shutting down the Derby system: http://db.apache.org/derby/docs/10.4/devguide/tdevdvlp20349.html "If the application that started the embedded Derby quits but leaves the JVM running, Derby continues to run and is available for database connections." What happens if you re-try your test, but fully shut down the Derby system? thanks, bryan