users
[Top] [All Lists]

Re: [cinjug-users] ResultSet closing prematurely

To: "Jason Kretzer/STAR BASE Consulting Inc." <JKretzer@xxxxxxxxxxxxxxx>
Subject: Re: [cinjug-users] ResultSet closing prematurely
From: Greg Williams <greg@xxxxxxxxxxxxxxxx>
Date: Thu, 20 May 2004 16:39:10 -0400
Cc: users@xxxxxxxxxx
Delivered-to: mailing list users@cinjug.org
In-reply-to: <OFE4CE3EBF.40221676-ON85256E9A.006F6AA2-85256E9A.006F7DB6@starbaseinc.com>
Mailing-list: contact users-help@cinjug.org; run by ezmlm
References: <OFE4CE3EBF.40221676-ON85256E9A.006F6AA2-85256E9A.006F7DB6@starbaseinc.com>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
I know this seems like the obvious, but check for an misplaced call to rs.close() within your while loop.  We've all made simple mistakes like this that drive us nuts.

Greg

Jason Kretzer/STAR BASE Consulting Inc. wrote:

I have a query that returns two records and using a standard while loop, I get the records.  For some reason the loop is only entered once and then I get the exception at the bottom on the second iteration.  The exception references the while(rs.next())

Anyone know what could cause this?




ResultSet rs = stmt.executeQuery("some_query");

while(rs.next())
{
        //do something with rs
}




com.ibm.db2.jcc.b.SQLException: Invalid operation: result set closed
<Prev in Thread] Current Thread [Next in Thread>