Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 55856 invoked from network); 11 Apr 2007 14:31:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Apr 2007 14:31:04 -0000 Received: (qmail 84627 invoked by uid 500); 11 Apr 2007 14:31:01 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 84596 invoked by uid 500); 11 Apr 2007 14:31:01 -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: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 84571 invoked by uid 99); 11 Apr 2007 14:31:01 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Apr 2007 07:31:01 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Apr 2007 07:30:53 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4F26871407B for ; Wed, 11 Apr 2007 07:30:33 -0700 (PDT) Message-ID: <7971758.1176301833321.JavaMail.jira@brutus> Date: Wed, 11 Apr 2007 07:30:33 -0700 (PDT) From: "John H. Embretsen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2480) DriverManager.getConnection leaks memory when connecting to a non-existent database In-Reply-To: <659846.1174597652175.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488090 ] John H. Embretsen commented on DERBY-2480: ------------------------------------------ Assigning this issue to myself while I'm trying to figure out the best way to integrate a test for this into Derby's JUnit test framework. It seems that there is currently no support for trying to connect to a database without also creating it if it does not already exist. I won't be working full time on this, so feel free to reassign if desired. > DriverManager.getConnection leaks memory when connecting to a non-existent database > ----------------------------------------------------------------------------------- > > Key: DERBY-2480 > URL: https://issues.apache.org/jira/browse/DERBY-2480 > Project: Derby > Issue Type: Bug > Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6, 10.2.2.0, 10.3.0.0 > Environment: Windows Vista, JDK 1.4.2_13 > Solaris 10, Sun JDK 1.4.2, 1.5.0 & 1.6.0 > Red Hat Enterprise Linux 4 (2.6.9-34.ELsmp_64), Sun JDK 1.5.0 & 1.6.0 > Reporter: Jeff Clary > Assigned To: John H. Embretsen > Priority: Minor > Attachments: DERBY-2480-1.diff, derbyall_report.txt, heap-server-Xmx32m.png, Patch_DERBY-1947_and_DERBY-2480.diff, testOpenOfMissingDatabase.java > > > Repeated calls to java.sql.DriverManager.getConnection("jdbc:derby:C:\\DOES_NOT_EXIST") leak memory and eventually lead to an OutOfMemoryError. > This bug is similar to DERBY-1947 in that ContextManager objects are not getting removed from the HashSet. The attached test program demonstrates the issue. When run with VM options -Xms8m -Xmx8m, it throws an OutOfMemoryError after 19022 calls to DriverManager.getConnection. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.