[maven-release-plugin] prepare for next development iteration
Using H2 1.3.175
race condition could lead to using a Timer that was already canceled
prepare release
adapted to H2 1.3.176
[maven-release-plugin] prepare release h2ha-1.3.176.1
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] rollback the release of h2ha-1.3.176.1
[maven-release-plugin] prepare release h2ha-1.3.176.1
[maven-release-plugin] rollback the release of h2ha-1.3.176.1
[maven-release-plugin] prepare release h2ha-1.3.176.1
[maven-release-plugin] rollback the release of h2ha-1.3.176.1
[maven-release-plugin] prepare release h2ha-1.3.176.1
[maven-release-plugin] prepare for next development iteration
overriding mavn release plugin version
Merge branch '1.3.174'
race condition on client connection retry
on windows it seems to take a few milliseconds until the
DB data reaches the disk after commit - we introduce a
delay for that
avoiding a possible deadlock on large DB files by  
allowing the server to process messages while it is sending 
checksums
multiple reconnects of a client caused NPEs