Return-Path: 
 <derby-user-return-6410-apmail-db-derby-user-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-user-archive@www.apache.org
Received: (qmail 57923 invoked from network); 16 Mar 2007 13:40:01 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 16 Mar 2007 13:40:01 -0000
Received: (qmail 19599 invoked by uid 500); 16 Mar 2007 13:40:08 -0000
Delivered-To: apmail-db-derby-user-archive@db.apache.org
Received: (qmail 19579 invoked by uid 500); 16 Mar 2007 13:40:08 -0000
Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-user-help@db.apache.org>
list-unsubscribe: <mailto:derby-user-unsubscribe@db.apache.org>
List-Post: <mailto:derby-user@db.apache.org>
List-Id: <derby-user.db.apache.org>
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Delivered-To: mailing list derby-user@db.apache.org
Received: (qmail 19564 invoked by uid 99); 16 Mar 2007 13:40:08 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2007 06:40:08 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [65.213.51.212] (HELO virgilearp.actuate.com) (65.213.51.212)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2007 06:39:57 -0700
Received: from exchange8.actuate.com (Not Verified[192.168.3.4]) by
 virgilearp.actuate.com with MailMarshal (v6,1,4,441)
	id <B45fa9f5b0001>; Fri, 16 Mar 2007 05:44:59 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Heap container closed exception (2 statements on same connection)
Date: Fri, 16 Mar 2007 06:39:22 -0700
Message-ID: <71F491F5DA99604A80DE49424BF3D02B3EBB8C@exchange8.actuate.com>
In-Reply-To: <45F9C97D.4080809@amberpoint.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Heap container closed exception (2 statements on same
 connection)
Thread-Index: AcdnUeSKpKoaRez+TGm7weQtjIXOUgAfBjtA
References: <71F491F5DA99604A80DE49424BF3D02B3EB7C8@exchange8.actuate.com>
 <45F9C97D.4080809@amberpoint.com>
From: "Jeffrey Clary" <jclary@actuate.com>
To: "Derby Discussion" <derby-user@db.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

I expected to be able to retrieve all 500 rows from the result set with
no exception.  I am not experienced with the holdability attribute, but
as I understand it, it allows a result set in a connection to stay open
across commits, either explicit or implicit. =20

I have run the same test after calling
Connection.setHoldability(ResultSet.CLOSE_CURSORS_AT_COMMIT).  With
setting, the very first call to next() fails with an exception
indicating that the result set is not open.  That makes sense to me,
because the other statement (creating an unrelated table) triggered an
implicit commit.  However, with holdability set to
HOLD_CURSORS_OVER_COMMIT, I no longer get an exception on calling next()
the first time, but rather get good data for 415 calls.  On the 416th
call, I get an exception not that the result set is closed, but rather
than an underlying storage mechanism is closed. =20

I'm mostly looking for some feedback that this is a bug, rather than
Derby working as designed, before I go over to the derby-dev mailing
list to talk about it.

Jeff

-----Original Message-----
From: Bryan Pendleton [mailto:bpendleton@amberpoint.com]=20
Sent: Thursday, March 15, 2007 5:32 PM
To: Derby Discussion
Subject: Re: Heap container closed exception (2 statements on same
connection)

> java.sql.SQLException: The heap container with container id=20
> Container(-1, 1173965368428) is closed.

Hi Jeff,

I don't have a lot to offer on this problem, but I did try
your test program and I get the same exception, so the problem
reproduces for me.

What was the behavior that you expected to see, instead of the
exception?

thanks,

bryan