So I disabled MVCC by changing my database URLs to be: jdbc:h2:ssl:// 192.168.1.9:35001/var/data/Prod_Database/Server_Util-DB;MVCC=FALSE <http://192.168.1.9:35001/var/data/Prod_Database/Server_Util-DB>
After restarting the production application I see that the boolean flag in the INFORMATION_SCHEMA.SETTINGS table has updated to FALSE so it appears that the change was taken. However, after re-running a batch process overnight I see that the change has had no effect on the memory consumption. The batch still failed from the database exhausting its 2G heap and the JConsole output still looks like the graph that I posted initially. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
