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 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
Unfortunately, it proves to me that our MULTI_THREADED=1 support
is not at all safe.
For example, in the stacktrace below:
...
The layers up to org.h2.command.CommandContainer are synchronized
around the Session object.
And the layers from org.h2.store.PageStore down are synchronized
around the PageStore object.
But the layers in between have no synchronization, but they are
shared between multiple sessions.
I am afraid I have no idea how to fix this, and it looks like
quite a big job.
--
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 h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/groups/opt_out.
