Thanks Thomas. I appreciate the assistance.
- Did you use SHUTDOWN DEFRAG?
No
- How many connections does your application use concurrently?
One global H2 connection per process. I am suspecting that may be the
cause of this problem, if Connections cannot be concurrently shared
amongst multiple threads?
- Do you use temporary tables?
No
- Did you use LOG=0 or LOG=1?
Not sure what this option is referring to. We're just using the
default, whatever that is.
- 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.
1.3.155
- 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)?
No
- Do you use any H2-specific system properties?
No
- Is the application multi-threaded?
Yes (approximately 10 concurrent threads).
- What operating system, file system, and virtual machine
(java -version) do you use?
Red Hat Enterprise Linux
ext3 filesystem
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
- How did you start the Java process (java -Xmx... and so on)?
-Xmx5000m -XX:SoftRefLRUPolicyMSPerMB=1 -XX:+AggressiveHeap -XX:-
UseGCOverheadLimit
- Is it (or was it at some point) a networked file system?
no
- How big is the database (file sizes)?
approx. 16kb when the corruption occurred.
- How much heap memory does the Java process have?
5gb
- Is the database usually closed normally, or is process terminated
forcefully or the computer switched off?
closed normally
- Is it possible to reproduce this problem using a fresh database
(sometimes, or always)?
We have now seen these at 4 separate deployments. It does appear to
consistently recur after restarting with a fresh database.
- 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?
I will request the .trace.db information and send as soon as I get it.
- Could you send the .h2.db file where this exception occurs?
I have emailed the file to you.
--
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.
