Your best bet at debugging out of memory problems is to
(1) add the -XX:+HeapDumpOnOutOfMemoryError option to your command line
(2) run the program. when it crashes, it will produce a file with a name
like java_1305.hprof
(3) analyze the dump with something like Eclipse MAT:
http://blog.bosch-si.com/how-to-analyze-leaky-webapps/
http://www.slideshare.net/BonitaSoft/first-steps-with-mat
On 2012-10-19 07:13, priyanka priya wrote:
jdbc:h2:tcp://localhost/~/abc;
jdbc:h2:tcp://localhost/~/abc;mvcc=true;lock_timeout=100000;auto_reconnect=true;auto_server=true
Out of memory.; SQL statement:
SCRIPT [90108-169]
<https://192.168.123.109:8082/tools.do?jsessionid=e9ff1c9826858a84d39747b47fa8a5cb#>
90108/90108 (Help)
<http://h2database.com/javadoc/org/h2/constant/ErrorCode.html#c90108>
--
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.
