Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 55540 invoked from network); 29 Oct 2010 02:48:06 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Oct 2010 02:48:06 -0000 Received: (qmail 67207 invoked by uid 500); 29 Oct 2010 02:48:06 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 67005 invoked by uid 500); 29 Oct 2010 02:48:05 -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 66996 invoked by uid 99); 29 Oct 2010 02:48:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Oct 2010 02:48:04 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bpendleton.derby@gmail.com designates 209.85.161.172 as permitted sender) Received: from [209.85.161.172] (HELO mail-gx0-f172.google.com) (209.85.161.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Oct 2010 02:47:59 +0000 Received: by gxk7 with SMTP id 7so1859323gxk.31 for ; Thu, 28 Oct 2010 19:47:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Q6EXopcOSsLmkPuO30IOqFAIYSj2ylkZtcDDov3oCGw=; b=Sr5l9C1LNlFIDUzXWdL4GetD/gu+aTSWpBz+8N1BnF6KseFPNPGV2kReiIuBCtAlfM 9khh4jX+wzKw+/R0U6ebOt+G0UndtO5FKZjQsF+5Qv6qjwbQ96HxGnhAjYFKLAt35CIX tJurdyjgo6+/xfz2Y8yKVxZLCuUvHNML1lK9Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=QRyUeSqhKErXofE/dOmLPg+mP6wdB5/mjkuyMQrPe2TNX46MQUsW39QbHPxVfD2TRe l7/ceQ+jAufx6bopzCpdGwlTXIrul14rnyP4/jxjr+HVGJEN3W26tCgNGengUv/bC+aK toslWslPuN2ItdciuOTHfZslhHG52E8HvblxA= Received: by 10.151.12.11 with SMTP id p11mr2592213ybi.385.1288320458177; Thu, 28 Oct 2010 19:47:38 -0700 (PDT) Received: from [192.168.0.103] (c-67-170-231-73.hsd1.ca.comcast.net [67.170.231.73]) by mx.google.com with ESMTPS id q36sm1320467ybk.18.2010.10.28.19.47.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 Oct 2010 19:47:37 -0700 (PDT) Message-ID: <4CCA35C6.2080608@gmail.com> Date: Thu, 28 Oct 2010 19:47:34 -0700 From: Bryan Pendleton User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.9) Gecko/20100922 Thunderbird/3.1.4 MIME-Version: 1.0 To: Derby Discussion Subject: Re: java.lang.RuntimeException: java.sql.SQLException: ResultSet not open References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To turn autocommit off, call Connection.setAutoCommit(false); Here's some docs: http://download.oracle.com/javase/1.4.2/docs/api/java/sql/Connection.html If you don't turn autocommit off, you will indeed discover that the automatic commit process can close various cursors and result sets at awkward times: http://db.apache.org/derby/docs/10.6/devguide/cdevconcepts29416.html You can gain a better understanding of the behavior of your application by learning to read the derby.log logfile, and by learning to use the various Derby trace flags, such as derby.language.logStatementText. If you can post more details about the specifics of your situation, the community will be able to give you more detailed suggestions. thanks, bryan