From ca14a193647130cb14f8109e1df3a0d890b15a33 Mon Sep 17 00:00:00 2001 From: Pavol Mederly Date: Wed, 31 May 2017 20:20:11 +0200 Subject: [PATCH] Solving H2 1.4 slowness? --- .../com/evolveum/midpoint/repo/sql/SqlRepositoryFactory.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/repo/repo-sql-impl/src/main/java/com/evolveum/midpoint/repo/sql/SqlRepositoryFactory.java b/repo/repo-sql-impl/src/main/java/com/evolveum/midpoint/repo/sql/SqlRepositoryFactory.java index fa289ded705..3a5ad79bf79 100644 --- a/repo/repo-sql-impl/src/main/java/com/evolveum/midpoint/repo/sql/SqlRepositoryFactory.java +++ b/repo/repo-sql-impl/src/main/java/com/evolveum/midpoint/repo/sql/SqlRepositoryFactory.java @@ -170,7 +170,7 @@ private void normalizeConfiguration(SqlRepositoryConfiguration config) throws Re //Both read locks and write locks are kept until the transaction commits. jdbcUrl.append(";LOCK_MODE=1"); //fix for "Timeout trying to lock table [50200-XXX]" in H2 database. Default value is 1000ms. - jdbcUrl.append(";LOCK_TIMEOUT=10000"); + jdbcUrl.append(";LOCK_TIMEOUT=100"); // experimental setting - let's resolve locking conflicts by midPoint itself //we want to store blob datas (full xml object right in table (it's always only a few kb) jdbcUrl.append(";MAX_LENGTH_INPLACE_LOB=10240");