Hi. How much memory are you making available to the JVM? I've had a similiar issue, but it turned out that I simply had to make more memory available to my Java Runtime with the -Xmx parameter. I solved this by using a small batch file to start the application, it also creates a neat little console that I use during debugging if I use java to start the application. I then switch to javaw when I go to production, hiding the little console.
For example (development code), I put all of this in a batch file called runner.bat: @echo off @cls @start java -Xmx512m -jar POSClient.jar Once I'm happy and am deploying on the client side, I change the code to use the javaw application: @echo off @cls @start javaw -Xmx512m -jar POSClient.jar This works quite well on Windows machines, of course on my Linux box I use a little script, but that's mostly for servers and development, very very few of my clients actually use Linux for workstations. Best regards Ewald -- 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.
