Ok, I just filed issue 398 and included a link to the gzipped trace file there. Good luck!
-Sandeep On Thursday, May 10, 2012 1:32:28 PM UTC-7, Sandeep Tamhankar wrote: > > It's definitely a 1.3.166 db. My application starts with a clean h2 db and > is loading the db from an xml file (exported from our application > previously). I was hoping the stack trace I reported would be enough info > for you because it took about 36 hours and a 19GB database before the > failure occurred. > > However, just yesterday a colleague ran into a similar error while > importing an xml file where his failure occurred after about an hour. This > leads me to believe there's something about the structure of our data that > leads to this case. I'll spend some time today trying to shrink the failure > scenario to as small amount of data/time as possible and get back to you. > > -Sandeep > > On Tuesday, May 8, 2012 11:43:21 PM UTC-7, Thomas Mueller wrote: >> >> Hi, >> >> Not for me, unfortunately. Running 1.3.166, embedded in my app >> >> >> Could you check that the database file was created with version 1.3.166? >> To do this, run the statement >> >> SELECT * FROM INFORMATION_SCHEMA.SETTINGS >> WHERE NAME='CREATE_BUILD' >> >> The result should be 166. If it is, could you send me a reproducible test >> case if that's possible? >> >> Regards, >> Thomas >> >> -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/jOFdE2o5eVcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
