commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen Westbom <>
Subject Re: commons dbcp - random exhausted resultsets
Date Wed, 15 Jan 2003 01:25:21 GMT

Can you get a stack trace?  There are two bugs with multiple result set handling in the result
set wrapper class within the dbcp package in the next() and close() wrapper methods.  I fixed
them on my sandbox and sent them to the commons package owner email address describing the
The bug I get is a null pointer exception in mine, not an exhausted error, but this was using
Sybase's ResultSet and CallableStatement implementations, not Oracle's.  The same problem
could be manifested differently with Oracle.
 Takeshi L Toyohara <> wrote:hey all,

just wondering if anyone has had a similar issue with getting the ol
SQLException: Exhausted ResultSet, even though i have a while(

running tomcat4 (4.0 and 4.1)
oracle 9i
using the commons dbcp as the connection pool as described in the tomcat
conn pool FAQ (oracle 9i thin driver)

here's the code snippet thats barfing. there is not a pattern to how many
times through the while loop it goes before it fails and spits up the
SQLException. anyone have any thoughts on the matter?

some more info: i printed out the value of and its "true" right
before i get the Exhausted ResultSet exception. fairly interesting...

thanks in advance

rs = DBU.executeQuery(SQL, args);

while (
currIntID = rs.getString(1); // this statement throws an exception after
// times through the while() loop


Takeshi L Toyohara
Cauldron Solutions
Solutions Developer
212.696.1600x20 (office)
212.696.2336 (fax)

To unsubscribe, e-mail: 
For additional commands, e-mail: 

Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message