> PreparedStatement pstmt = connection.prepareStatement(........);
> ...
> ResultSet rs = pstmt.executeQuery();
> while(rs)
> {
> a lot of small request generated from rs content
> }
Most likely the problem is that the result set is closed while
processing the nested requests. Currently H2 uses a list of 64 open
JDBC objects per session. Theoretically H2 could use garbage
collection, but that's slow and not reliable. You can change the limit
using the system property h2.serverCachedObjects - see also
http://www.h2database.com/javadoc/org/h2/constant/SysProperties.html#h2.serverCachedObjects
You can set the limit higher. This shouldn't be a problem unless you
use many connections.
Please tell me if this doesn't solve the problem.
Regards,
Thomas
--You received this message because you are subscribed to the Google Groups "H2 Database" group.To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/_3rIC6aaacEJ.
To post to this group, send email to h2-da...@googlegroups.com.
To unsubscribe from this group, send email to h2-database...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.