(Sorry about the double post, I made a mess of my previous post by trying to edit it.)
So I wished to do some testing about how H2 behaves in multi-threaded mode. Only, I'm not entirely certain if it's entering multi-threaded mode. When I test with 1.4.196 (latest version from GIT), the following happens: 1) Connect jdbc:h2:tcp://127.0.0.1:9092/db;MULTI_THREADED=1;DB_CLOSE_DELAY=-1 2) Verify: SELECT * FROM INFORMATION_SCHEMA.SETTINGS WHERE name IN ('MVCC', 'MULTI_THREADED','DB_CLOSE_DELAY'); NAME VALUE DB_CLOSE_DELAY -1 MULTI_THREADED 1 MVCC TRUE MULTI_THREADED false So it returns both "MULTI_THREADED false" and "MULTI_THREADED 1" and I am confused. I stop the service and retry another way (still with 1.4.196): 1) Connect jdbc:h2:tcp://127.0.0.1:9092/db;MULTI_THREADED=TRUE;DB_CLOSE_DELAY=-1 2) Verify: SELECT * FROM INFORMATION_SCHEMA.SETTINGS WHERE name IN ('MVCC', 'MULTI_THREADED','DB_CLOSE_DELAY'); NAME VALUE DB_CLOSE_DELAY -1 MULTI_THREADED 1 MVCC TRUE MULTI_THREADED false Finally, being quite confused, I revert to 1.4.190 for double-checking (I download the zip file and compile locally, just like I did with the Git HEAD version) and do like this: 1) Connect jdbc:h2:tcp://127.0.0.1:9092/db;MULTI_THREADED=1;DB_CLOSE_DELAY=-1 2) Verify: SELECT * FROM INFORMATION_SCHEMA.SETTINGS WHERE name IN ('MVCC', 'MULTI_THREADED','DB_CLOSE_DELAY'); NAME VALUE DB_CLOSE_DELAY -1 MULTI_THREADED 1 MVCC TRUE MULTI_THREADED false I am currently reading the sources too, but how should I interpret the result of "false" and "1" returned together? -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.