Hi,
H2 (ver. 2011-03-14) gives me "the object is already closed" exception
for a call to ResultSet#next().
I understood from previous messages about this post, that this could
be caused by keeping too many JDBC objects alive at the same time. At
the time of this exception I have 23 PreparedStatement's and 2
ResultSet's (at least these are what I know about).
I tried to increase limits by running this before loading the driver:
System.setProperty("h2.serverCachedObjects", "20000");
but I didn't see any effect.
When I run same program with HSQLDB, then everything goes fine.
Is there something I could do to track down the problem? Can I somehow
ask from Connection, how many this kind of objects are alive?
greetings,
Aivar
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
