Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 57940 invoked from network); 6 Sep 2005 04:08:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Sep 2005 04:08:04 -0000 Received: (qmail 43207 invoked by uid 500); 6 Sep 2005 04:08:03 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 43182 invoked by uid 500); 6 Sep 2005 04:08:02 -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 43169 invoked by uid 99); 6 Sep 2005 04:08:02 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2005 21:08:02 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS,SPF_HELO_FAIL X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.143] (HELO e3.ny.us.ibm.com) (32.97.182.143) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2005 21:08:15 -0700 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e3.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id j8647wFn012129 for ; Tue, 6 Sep 2005 00:07:58 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j8647wIc068252 for ; Tue, 6 Sep 2005 00:07:58 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id j8647wCu022563 for ; Tue, 6 Sep 2005 00:07:58 -0400 Received: from [127.0.0.1] (sig-9-48-114-0.mts.ibm.com [9.48.114.0] (may be forged)) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id j8647ueb022520 for ; Tue, 6 Sep 2005 00:07:58 -0400 Message-ID: <431D161B.9090301@sbcglobal.net> Date: Mon, 05 Sep 2005 21:07:55 -0700 From: Kathey Marsden User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Discussion Subject: Re: Momory leak in JDBC driver? References: <20050902171122.55806.qmail@web52503.mail.yahoo.com> <20050905114934.GB15666@atum01.norway.sun.com> In-Reply-To: <20050905114934.GB15666@atum01.norway.sun.com> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Bernt M. Johnsen wrote: >>>>>>>>>>>>>Dyre.Tjeldvoll@Sun.COM wrote >>>>>>>>>>>>> >> >>Two things: >> >>1) Are you closing your ResultSets? If just let the ResultSet objects >> pass out of scope without closing them, they will be "leaked". That >> is, the driver keeps a linked list of them so they won't be >> gc'ed. I have experienced this myself, but I don't know if there is >> a JIRA issue for it >> >> > >Slike ting kan fikses med WeakReference... > > I know about this issue for Prepared Statements, http://issues.apache.org/jira/browse/DERBY-210, but was not aware of it for ResultSets. If there is a separate issue for ResultSets please file it. java org.apache.derby.drda.NetworkServerControl runtimeinfo shows all open prepared statements so can be used to determine if DERBY-210 is the issue in this case. The workaround is to explicitly close the prepared statements. Regarding a code solution, I don't know about the Norwegian part, but "blah, blah WeakReference" sounds right to me. It would be nice to see someone pick up this bug for 10.1.2. Kathey