I'm using the embedded version. Here's how I create the connection:
System.setProperty("h2.serverCachedObjects", "20000");
Class.forName("org.h2.Driver");
String path =
AlvorCachePlugin.getDefault().getStateLocation().append("/
cache_h2").toPortableString();
String url = "jdbc:h2:" + path + ";TRACE_LEVEL_FILE=3";
return DriverManager.getConnection(url, "SA", "");
The shortest trace I could create while still reproducing the
exception is 288KB, so I uploaded it here:
http://aivarannamaa.ee/cache_h2.trace.zip
I counted again the maximum number of open ResultSet-s, and can now
confidently say that it's 4 (when running the same program that
produced the trace, but using HSQLDB). In addition there are 23 open
PreparedStatement-s and 1 Connection. I need several open ResultSet-s
for retrieving recursive data structures.
regards,
Aivar
On Mar 23, 9:33 pm, Thomas Mueller <[email protected]>
wrote:
> Hi,
>
> > I tried to increase limits by running this before loading the driver:
> > System.setProperty("h2.serverCachedObjects", "20000");
>
> You need to set this property on the server. For example, if you start
> the server using the command line, use:
>
> java -Dh2.serverCachedObjects=20000 ...
>
> 20000 is probably too much, but let's try. If this is really the
> problem then I would like to find out why it fails for you. Could you
> please use a higher log level (append ;TRACE_LEVEL_FILE=3 to the
> database URL) and post or send me the *.trace.db files from both the
> server and the client(s)?
>
> Regards,
> Thomas
--
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.
