Hi again, We've updated to version 1.2.140 two weeks ago and haven't seen the error again.
Thanks a lot for your help! On Jul 15, 1:45 pm, Borja <[email protected]> wrote: > Hi, > > As I've said, we're using the DB through JBoss messaging. We have > several queues (each one with their own tables), but all in the same > DB file. Maybe there's a problem of concurrence due to multiple > threads? Is there any way for me to check this or gather more info > about how H2 is being used by JBoss? > > Thanks. > > On Jul 10, 11:04 am, Thomas Mueller <[email protected]> > wrote: > > > Hi, > > > So far I don't know what the problem could be. The memory mapped file > > system doesn't behave exactly like the regular file system (seeking > > past the end of the file is not allowed currently) and I will fix > > that. However, I don't think that's the problem here. I ran the unit > > test of H2 with the "nioMapped:" prefix and didn't find a problem. > > > I'm not sure why the capacity and limit is lower than the file size in > > your case. Could it be that another process is running concurrently > > and changing the database file at the same time? You don't use the > > option FILE_LOCK, or backup / restore the database file concurrently, > > right? I guess not... > > > So far the only think I can do is improve the behavior of the memory > > mapped file system to more closely match the regular file system, > > improve error messages. > > > Regards, > > Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. 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.
