Hi Noel, My connection URL is essentially this: "jdbc:h2:tcp://server1:9092,server2:9092/./folder/dbName"
I have now added ";TRACE_LEVEL_FILE=4" to the URL to switch to SLF4J logging. We do not use any other DB options via SET commands or environment variables. Please note that 2 applications are accessing the cluster. I have now started to look at the H2 source code and from what I can see our system is experiencing transient problems when running updates on server1 which then results in the updates only making it to server2. I then think that another connection (as we use a pool) attempts to read the data from server1 but it doesn't exist. It looks like the cluster list is held per connection, is this correct? Regards, Dan On Thursday, 22 August 2013 16:07:20 UTC+1, Noel Grandin wrote: > > Don't think I can help much because I don't use clustering, but let's > rule out the obvious problems anyhow :-) > �- what does your DB URL look like? > -� are you setting any other DB-level options via SET commands or > environment variables? > > -- Noel. > > On 2013-08-19 13:26, Daniel Stone wrote: > > Data loss with H2 HA / Clustered Mode > > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
