> OK, I can't see anything useful in the trace log. > > So let's run through Thomas' checklist - sorry but this going to be a > little long winded: >
That's ok :-) > > - What is your database URL? > jdbc:h2:~/data/rcl;LOCK_TIMEOUT=86400000;MULTI_THREADED=1 The database is embedded in my application. - Did you use LOG=0 or LOG=1? Did you read the FAQ about it? > No, I don't use LOG > - Did the system ever run out of disk space? > No. (For sure, 3 TB free disk space :-) > - Could you send the full stack trace of the exception including message > text? > I've sent the trace log to you so you should already have it. > - Did you use SHUTDOWN DEFRAG or the database setting DEFRAG_ALWAYS with > H2 version 1.3.159 or older? > The database was created with 1.3.173, so 1.3.159 was never used with the database. I am using SHUTDOWN DEFRAG once per week. > - How many connections does your application use concurrently? > I am using the JdbcConnectionPool. Using this pool there are not more than 10 parallel connections. I am also running the H2 webserver. So there might be one additional connection. > - Do you use temporary tables? > No. > - With which version of H2 was this database created? > You can find it out using: > select * from information_schema.settings where name='CREATE_BUILD' > or have a look in the SQL script created by the recover tool. > The recovered SQL file tells: INSERT INTO O_0 VALUES(1, 0, 6, 'SET CREATE_BUILD 173'); > - Did the application run out of memory (once, or multiple times)? > No. > - Do you use any settings or special features (for example cache settings, > two phase commit, linked tables)? > Usually not. With this database I created one linked table once. But removed it instantly. > - Do you use any H2-specific system properties? > No > - Is the application multi-threaded? > Yes > - What operating system, file system, and virtual machine > (java -version) do you use? > Filesytem is ext4 on OpenSUSE 11.2, 64 bit kernel 2.6.31.14-0.8-default #1 SMP Java(TM) SE Runtime Environment (build 1.7.0_11-b21) Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode) > - How did you start the Java process (java -Xmx... and so on)? > Here are the interesting parts: java -Xmx4g -XX:-UseSplitVerifier -cp myapp.jar com.xxx.xxx.xxx.MyApp <some parameter of the app> > - Is it (or was it at some point) a networked file system? > No > - How big is the database (file sizes)? > ~ 125 GB - How much heap memory does the Java process have? > 4 GB > - Is the database usually closed normally, or is process terminated > forcefully or the computer switched off? > Usually the database is closed once a week by running SHUTDOWN DEFRAG. It is possible that the database gets closed due to shutdown the server. > - Is it possible to reproduce this problem using a fresh database > (sometimes, or always)? > I've seen this with a fresh database but I cannot give a testcase that triggers the problem. > - Are there any other exceptions (maybe in the .trace.db file)? > Could you send them please? > - Do you still have any .trace.db files, and if yes could you send them? > - Could you send the .h2.db file where this exception occurs? > > 125GB... Do you really want to have it? Thanks for having a look on it! 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 http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
