no reason to be parsimonious here, can only help

CI still failing, maybe we have a memory leak somewhere in the tests?

so performance doesn't bottleneck on the synchronization in the FileBase
default implementations

otherwise client code will end up calling the version in FileBase, which
has unnecessary synchronisation

so we don't get warnings about the overriding methods also needing to be
synchronized, which is not the case

we're not interesting in exceptions in closing in these tests

since we require Java7, this is no longer necessary

to give us a thread dump when they get stuck

About #385 

Fix multi-threaded mode insert exception "Unique index or primary key violation", test case by Anatolii K

so we get nicer error messages when things fail

when run in memory mode, the initial connection used a memory DB,while
the second connection used a disk DB

doing DROP ALL OBJECTS

leads to an NPE when the session closes