Hi,
Thanks a lot! I can now reproduce the problem. I have a simpler test case.
The problem seems to be a combination of auto-commit disabled (this was the
missing piece for me so far), runscript, and set cluster.
Connection conn = DriverManager.getConnection("jdbc:h2:mem:test");
conn.setAutoCommi
Hi,
I have a fix and will commit it in trunk. A workaround is to enable
autocommit for the "runscript" part.
Regards,
Thomas
On Thursday, March 19, 2015, Eric Chatellier
wrote:
> Le 19/03/2015 07:45, Thomas Mueller a écrit :
> > Hi,
> >
> > The settings can be changed in any order... Does it c
Le 19/03/2015 07:45, Thomas Mueller a écrit :
> Hi,
>
> The settings can be changed in any order... Does it consistently work in one
> case, but not the other?
Yes, it consistently fails if "set cluster ''" is not the first instruction.
In the same sql file, if i modify script just to set "set clus
Hi,
The settings can be changed in any order... Does it consistently work in
one case, but not the other?
Could you try with the latest version of H2, and append ";mv_store=false"
to the database URL? I can't reproduce the problem with the latest version,
and I didn't try yet with the version you
Le 17/03/2015 16:24, Eric Chatellier a écrit :
>
> I a modify a failing test with the java 8 file to set "SET CLUSTER '';" on the
> first line, the test is then ok.
>
> Can you confirm that this is a possible java 8 bug with SCRIPT TO command ?
I just found this :
http://docs.oracle.com/javase/8/do
Le 12/02/2015 12:36, Eric Chatellier a écrit :
> I can't isolate this bug, but i'm experiencing it 100% in my application.
>
> So, i've to idea how to fix this issue :(
Hi,
I think i finally find how to reproduce this bug.
This may be related to "SCRIPT TO" command, that got a different behaviour
Try to use the 'JDBC Probe' of JProfiler that migh give you an idea
- how connections are opened/closed
- what JDBC statements get executed
- what threads are involved
Am 12.02.2015 12:36, schrieb Eric Chatellier:
Le 02/02/2015 11:07, Eric Chatellier a écrit :
Now that Java 8 is becoming
Le 02/02/2015 11:07, Eric Chatellier a écrit :
> Now that Java 8 is becoming main line, and i always experiencing this bug, i
> will investigate harder...
I can't isolate this bug, but i'm experiencing it 100% in my application.
So, i've to idea how to fix this issue :(
--
Éric Chatellier - w
Le 09/12/2014 18:03, Thomas Mueller a écrit :
> Hi,
>
> It looks like you are using "runscript" (RunScriptCommand in the stack trace).
> Is this all you do in your program at that time (nothing is happening
> concurrently)? If yes, could you post or send me the script file please?
Hi
I've tried to
Hi,
It looks like you are using "runscript" (RunScriptCommand in the stack
trace). Is this all you do in your program at that time (nothing is
happening concurrently)? If yes, could you post or send me the script file
please?
Regards,
Thomas
On Monday, December 8, 2014, Eric Chatellier
wrote:
Le 08/12/2014 08:17, Noel Grandin a écrit :
> what does your database URL look like?
>
I checked multiples parameters from:
jdbc:h2:file:/tmp/test/test;DEFAULT_LOCK_TIMEOUT=1000;DB_CLOSE_DELAY=0;LOCK_MODE=3;TRACE_LEVEL_FILE=0;TRACE_LEVEL_SYSTEM_OUT=0;LOG=1
to basic url:
jdbc:h2:file:/tmp/test/test
what does your database URL look like?
--
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
Hi,
I'm currently experiencing a "Timeout trying to lock table "SYS"" problem
only under Java 8 JVM.
With a java 7 JVM, everything is working fine.
I can't make a test case on it, because i can't understand what's is
involved.
The exception i get is :
Caused by: org.hibernate.PessimisticLockExc
13 matches
Mail list logo
