Was using an in-mem h2 db. When I switched it to w...
# tornadofx
b
Was using an in-mem h2 db. When I switched it to write to a file, everything is okay.
r
I'm recalling I had an issue similar to this when trying to use in-mem H2, ended up having the following database URL:
jdbc:h2:mem:dbname;DB_CLOSE_DELAY=-1
(
DB_CLOSE_DELAY=-1
being essential part)