Hi, I have a few questions:
- What is your database URL? - Did the application run out of memory (once, or multiple times)? - How did you start the Java process (java -Xmx... and so on)? - Is it (or was it at some point) a networked file system? - How big is the database (file sizes)? - How much heap memory does the Java process have? - Are there any other exceptions (maybe in the .trace.db file)? Could you send them please? - After how long do you usually get this problem? > Yes, I do set the java heap size. The problem is not JVM running out > of memory, but rather it seems that there is a slow memory leak from > the JVM to the OS into the nonpaged Kernel and eventually there is not > enough memory left that the database requires during the page loads. > So the machines with smaller Kernel sizes run out before the > connection establishes. Could you provide the link where you found this information, except for the one you aleady sent? I found this: http://support.microsoft.com/kb/272568 Possible cause: "Norton AntiVirus" http://www.coderanch.com/t/381258/Java-General/java/java-io-Exception-Insufficient-system Possible cause: "UNC Path" http://support.microsoft.com/kb/259837 Possible cause: "paged pool memory" > Do you think it would make a difference if I did not run the database > in embedded mode but rather as a local server? Or is the page IO the > same when establishing a connection? Yes, potentially it will help, however I think it should work without such tricks. H2 doesn't use a lot of resources. Both Java and H2 are used by many people without problems. I don't think there is a slow memory leak in the JVM that will show up in your case. 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.
