Hi Paul, I guess I was unclear. I believe it to be an H2 bug, not a Java bug. H2 was reusing calendar instances, sometimes without first calling the "calendar.clear()" method. By chance, this was okay with the way H2 used it, until a Java update with a revised timezone database file was issued.
The Moscow timezone changed in late 2014 from UTC+4 year-round to UTC+3 year-round, I understand. This issue seems to be related to the bug. I posted repro code and instructions in the pull request: https://github.com/h2database/h2database/pull/224 Even with the appropriate combination of Java version, H2 version, and timezone, the bug only occurred if particular dates were present in the database. See my pull request for a specific instance of when this happened. Regards, Steve On Wednesday, 30 December 2015 10:07:45 UTC+1, pwagland wrote: > > Hi Steve, > > Do you have more details as to what the bug is? And/or is there an > Oracle/OpenJDK issue reference for the bug? > > Cheers, > Paul > > -- 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.
