Hi everyone,
I'm using H2 database to store data in a desktop application.
I've developed an iterative test that:
- Opens the application
- Updates a single value from a row, from 'off' to 'on'
- Updates again the same row with the previous value, from 'on' to
'off'.
- Closes the application
and after 865 executions (that's just the last result, it failed
after 320, 700, ... iterations too) , the last update gets lost, and
in the next iteration (866), the value the test is changing in every
execution, is already set to 'on' (instead of 'off').
I'm using a cluster with two nodes. The first node is stored in a
hard drive, and second node in a memory card or in a virtual drive (a
subst drive in the same hard drive is storing the first node). When
I'm launching the test with hard drive / memory card configuration, it
completes 2500 iterations successfully; but with hard drive / virtual
drive configuration it always fails.
The data type the test is changing every time is a CLOB, and the
connection URL I'm using:
jdbc:h2:tcp://localhost:10110,localhost:10120/
clusting;DB_CLOSE_DELAY=-1;CACHE_TYPE=SOFT_LRU
Thanks in advance for your help.
--
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.
