Hi, I have seen that H2 uses System.currentTimeMillis() to check timeouts. This will fail in case the system time is changed (e.g. by ntp). In case the system time is shifted to future the timeouts will end much faster. In case the system time is shifted back the timeouts might take ages.
A good and safe alternative is to use the nanosecond timestamp given by System.nanoTime(). It is not bounded to the system time. It is strong ascending no matter how the system time jumps around. Uli -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
