Hi, > Well I use the localhost setting because I would think it's more > efficient.
Did you measure that it's more efficient (if yes: what is the difference on your system)? >> - With which version of H2 was this database created? > 133 That means the database file was created using H2 version 1.2.133. >> - How did you start the Java process (java -Xmx... and so on)? > -XX:NewSize=4096m -XX:MaxNewSize=4096m -XX:SurvivorRatio=4 - > XX:CMSInitiatingOccupancyFraction=70 -XX:+UseConcMarkSweepGC - > XX:PermSize=512m -XX:MaxPermSize=512m -Xms8g -Xmx8g Why do you use all those settings (except for -Xmx8g)? Did you run into problems when not using them? >> - Is the database usually closed normally, or is process terminated >> forcefully or the computer switched off? > The process is terminated forcefully, I will change that to call > connection.close() It shouldn't be a problem to terminate forcefully, but it's better to use Connection.close(). > one thread is using a ResultSet while another is running another query, could > that be a pb ? No. If it is possible, could you try to reproduce the problem if you re-create the database using the newest version, and without using the h2.bindAddress setting? This is just to make sure those factors don't affect the outcome. I'm still very interested to find and fix the problem of course. 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.
