Hi,
for the sake of completeness I have posted issue #539 that contains the
testcase and a link to this thread.
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
Hi Noel,
what a pity! Thanks for digging into the synching problems!
It sounds to me as if MULTI_THREADED=1 should never be used and its usage
is strongly inadvisable. Can you add some strong warnings to the
documentation so that other users do not fall into the same trap?
Thanks!
Uli
I've been using it in a production environment for several years without
issue. But it isn't very high concurrency, so I've probably just been
lucky that it hasn't had issues.
On 2/01/2014 4:39 PM, Uli wrote:
Hi Noel,
what a pity! Thanks for digging into the synching problems!
It sounds to
Hi,
The operations on RegularTable should be protected with the table level
locking mechanism, and each b-tree belongs to exactly one table. So in
theory it should work. But I understand there might be some bugs. My
priority is to get the MVStore ready, and then make multi-threading work.
On 2013-12-13 17:38, Uli wrote:
I managed to strip it down a bit more...
Thanks a lot for the test-case!
Unfortunately, it proves to me that our MULTI_THREADED=1 support is not at all
safe.
For example, in the stacktrace below:
java.lang.RuntimeException: Undo entry not written
Hi Noel,
I did have some time today and I managed to write a test case (for 1.3.174)
:-)
When running the application you should get:
General error: java.lang.RuntimeException: Undo entry not written; SQL
statement:
UPDATE values_7 SET timeend = 21332841064754 WHERE timeend =
I managed to strip it down a bit more...
--
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 h2-database+unsubscr...@googlegroups.com.
To post to this group, send
Hi
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:
- What is your database URL?
- Did you use LOG=0 or LOG=1? Did you read the FAQ about it?
- Did the system ever run out of disk space?
- Could you
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=8640;MULTI_THREADED=1
The database is embedded in my
Thanks for the extra info.
Could you perhaps try running your system with CHECK2 enabled?
Add an extra command line parameter like this:
-Dh2.check2=true
And see if you can trigger the problem?
Note that it will slow things down a little, but hopefully not so much
that it hides the
Ok, I will do that.
But first I have to recover the database and this will take some time...
I will post again if the error occurs again.
Uli
On Friday, September 20, 2013 2:01:11 PM UTC+2, Noel Grandin wrote:
Thanks for the extra info.
Could you perhaps try running your system with
Yeah, sorry, I have to warn you that I'm not hopeful of a quick fix -
these kinds of things are quite difficult to track down.
Without a test-case I'm shooting in the dark.
If you have limited time now you want to just try running your app with
MULTI_THREADED off, which is going to be more
I've updated to 1.3.173. Now I sometimes get the following Exception:
09-19 12:15:38 jdbc[2]: exception
org.h2.jdbc.JdbcSQLException: File corrupted while reading record:
page[61779266] b-tree leaf table:212525 entries:0. Possible solution: use
the recovery tool; SQL statement:
-- as
Did you start from a clean DB?
That looks like left-over corruption from the earlier problem.
You may have to do a dump and restore.
On 2013-09-19 14:49, Uli wrote:
I've updated to 1.3.173. Now I sometimes get the following Exception:
--
You received this message because you are subscribed
Yes, I started with a clean DB using 1.3.173.
Also yes that the database need to be restored.
I will email you the trace log. Maybe you can find some more information
about the problem.
Uli
On Thursday, September 19, 2013 3:03:58 PM UTC+2, Noel Grandin wrote:
Did you start from a clean DB?
Hi,
when using MULTI_THREADED=1 sometimes I get an exception when running a
query:
org.h2.jdbc.JdbcSQLException: General error: java.lang.RuntimeException:
page[50387075] data leaf table:124233 TEMP_RESULT_SET_124233 entries:0
parent:0 keys:null offsets:null parent 0 expected 50392430; SQL
This looks a lot of a temp -result-set bug I fixed in 1.3.173.
I suggest updating to the newer version.
On 2013-08-19 13:31, Uli wrote:
when using MULTI_THREADED=1 sometimes I get an exception when running
a query:
org.h2.jdbc.JdbcSQLException: General error:
java.lang.RuntimeException:
Great!
I'll try 1.3.173.
--
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 h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to
18 matches
Mail list logo
