Hi, 50 minutes are needed to open the connection after an unexpected VM shutdown with MVCC=TRUE, 30 seconds without this parameter. Something is going wrong in index rebuild in MVCC mode. Application seems to loop on redo method in pageStore class.
Here are some context details: Version used : 1.2.142 Database size : 40 MB Connection string : jdbc:h2:${jboss.server.home.dir}${/}database${/} editagDB;FILE_LOCK=SOCKET;CACHE_SIZE=0;AUTO_SERVER=TRUE;MVCC=TRUE| FALSE Actualy, playing with MVCC value only matters. We really need concurrent management control. Have you any idea or workaround? TIA -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to h2-datab...@googlegroups.com. To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.