Closed GoogleCodeExporter closed 9 years ago
Hi,
This looks like a serious problem. I have a few questions:
- What is your database URL?
- Did you use multiple connections?
- Did the application run out of memory (once, or multiple times)?
- Do you use any settings or special features (for example, the setting
LOG=0, or two phase commit, linked tables, cache settings)?
- Is the application multi-threaded?
- What operating system, file system, and virtual machine
(java -version) do you use?
- Is it (or was it at some point) a networked file system?
- 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?
- 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?
- Do you still have any .trace.db files, and if yes could you send them?
Regards,
Thomas
Original comment by thomas.t...@gmail.com
on 21 Dec 2009 at 4:04
- What is your database URL?
jdbc:h2:tcp://localhost//absolutepath;MULTI_THREADED=TRUE
- Did you use multiple connections?
My application used a single connection but I used the web inferface at the same time.
- Did the application run out of memory (once, or multiple times)?
Not that I know of.
- Do you use any settings or special features (for example, the setting
LOG=0, or two phase commit, linked tables, cache settings)?
MULTI_THREADED=TRUE but I just used it two access the db from the website while
the
query was runnning.
- Is the application multi-threaded?
No.
- What operating system, file system, and virtual machine
(java -version) do you use?
is stated above
- Is it (or was it at some point) a networked file system?
no
- How big is the database (file sizes)?
about 50MB
- How much heap memory does the Java process have?
I'm not sure but around 500-800MB
- Is the database usually closed normally, or is process terminated
forcefully or the computer switched off?
Normally not but when the queries didn't finish I had to kill the process.
- Is it possible to reproduce this problem using a fresh database
(sometimes, or always)?
Not really. I have used a fresh database and the query didn't finish but I
wasn't
able to reproduce the thrown exception.
- 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 don't have the failed .trace.db but my memory tells me and further tests
showed
that the file stays empty.
I want to correct the stated table sizes. The table classAssertionEnt has about
6k
rows and the table objectPropertyAssertion has about 36k rows. The tables are
joined
on columns that are primary keys and the column in the where condition is also
part
of a primary key.
Original comment by stefan.l...@gmail.com
on 22 Dec 2009 at 10:58
Could you try without using MULTI_THREADED=TRUE ? This setting is not fully
tested
yet. See also http://www.h2database.com/html/faq.html#reliable "Areas considered
experimental are". Also documented at
http://www.h2database.com/html/grammar.html#set_multi_threaded
I'm not saying it's not a bug, but that could be the reason.
Original comment by thomas.t...@gmail.com
on 22 Dec 2009 at 8:19
I change the bug to "works for me", because I don't have enough information to
reproduce the problem.
Original comment by thomas.t...@gmail.com
on 30 Jan 2010 at 3:01
Original issue reported on code.google.com by
stefan.l...@gmail.com
on 21 Dec 2009 at 3:34