I only checked my own log. This problem is not, for all intents and purposes, reproducible. We've seen it a few times over the years. So I cannot retry this with H2 trace logging on.
Later today I will try to post my analysis of the H2 code stack that I think could explain what I am seeing. I'd appreciate your feedback on it. On Wednesday, February 3, 2016 at 2:11:59 PM UTC-5, Noel Grandin wrote: > > One thing to ask - did you check the h2 trace log or just your own log? > Sometimes errors will show up there first. > On Wed, 03 Feb 2016 at 16:29, Stuart Goldberg <[email protected] > <javascript:>> wrote: > >> To my knowledge there is no such code. But if interrupt() might cause >> such a problem, it would seem to me that some other unforeseen exception >> might also cause that kind of problem. >> >> >> On Wednesday, February 3, 2016 at 8:04:41 AM UTC-5, Noel Grandin wrote: >>> >>> you don't by any chance have some other code that might be calling >>> "interrupt()" on the thread writing to the H2 >>> database file? >>> >>> That might conceivably cause such a problem. >>> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/h2-database. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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.
