Thanks for the reply. This is running on a client system where I can not easily interact with the system. Nothing urgent was lost, I'm mostly posting here so you know about it, but we can just recreate the data we need.
On Wed, Apr 28, 2010 at 3:24 PM, Thomas Mueller <[email protected]> wrote: > Hi, > > The stack trace is a bit strange, it says "PageDatallode" and not > "PageDataNode". I wonder how this happened? That's funny, this is just an OCR issue. I got the log files after it had been printed out and then rescanned. > > I have a few questions: > > - What operating system, file system, and virtual machine > (java -version) do you use? Some crazy IBM blade system. I'll get more info... > - How did you start the Java process (java -Xmx... and so on)? It is started via Tomcat > - What is your database URL? jdbc.url=jdbc:h2:file:/data/voyager/h2/dex;CACHE_SIZE=131072;CACHE_TYPE=LRU;WRITE_DELAY=2000 > - Did you use multiple connections? There is a connection pool yes. > - Do you use temporary tables? No temporary tables > - A workarounds is: use the tool org.h2.tools.Recover to create > the SQL script file, and then re-create the database using this script. > Does it work when you do this? Since nothing was lost, i don't want to bug them with messing with this. sorry. > - With which version of H2 was this database created? This was created with 1.2.132 > 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. > - Did the application run out of memory (once, or multiple times)? Yes this is possible. They said Tomcat crashed, but have not yet dug into the logs on how > - Do you use any settings or special features (for example cache settings, > two phase commit, linked tables)? > - Do you use any H2-specific system properties? I don't think so... > - Is the application multi-threaded? The application is multi-threaded, it connects to H2 via a connection pool (commons DBCP) > - Is it (or was it at some point) a networked file system? I don't think so, but I will check > - How big is the database (file sizes)? > - How much heap memory does the Java process have? > - Is the database usually closed normally, or is process terminated > forcefully or the computer switched off? apparently the system has crashed a few times. > - Is it possible to reproduce this problem using a fresh database > (sometimes, or always)? > - Are there any other exceptions (maybe in the .trace.db file)? > Could you send them please? I'll get them to look at the trace.db, but can only see stuff after it has been printed and then scanned :) > - 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? Doubt I can get the .db file, but will see what I can do. Thanks Ryan -- 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.
